Property talk:P157

From Wikidata
Jump to navigation Jump to search

Documentation

killed by
person who killed the subject
Descriptionperson who killed subject
Representsmurderer (Q931260)
Data typeItem
Domain
According to this template: person (Q215627), organism (Q7239)
According to statements in the property:
human (Q5) and fictional character (Q95074)
When possible, data should only be stored as statements
Allowed valuespeople (and maybe, in exceptional cases, entities, but probably not) (note: this should be moved to the property statements)
ExampleHolofernes (Q625748)Judith (Q3187975)
Archduke Franz Ferdinand (Q43063)Gavrilo Princip (Q80492)
Medusa (Q160730)Perseus (Q130832)
John F. Kennedy (Q9696)Lee Harvey Oswald (Q48745)
Tracking: usageCategory:Pages using Wikidata property P157 (Q26250065)
Lists
Proposal discussionProposal discussion
Current uses1,564
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Value type “human (Q5), fictional character (Q95074), organization (Q43229): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value human (Q5), fictional character (Q95074), organization (Q43229) (or a subclass thereof). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Value type Q5, Q95074, Q43229, SPARQL, SPARQL (new)
Type “human (Q5), fictional character (Q95074): element must contain property “instance of (P31)” with classes “human (Q5), fictional character (Q95074)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#type Q5, Q95074, SPARQL, SPARQL (new)
Item “place of birth (P19): Items with this property should also have “place of birth (P19)”. (Help)
List of this constraint violations: Database reports/Constraint violations/P157#Item P19, hourly updated report, search, SPARQL, SPARQL (new)
Item “date of birth (P569): Items with this property should also have “date of birth (P569)”. (Help)
List of this constraint violations: Database reports/Constraint violations/P157#Item P569, hourly updated report, SPARQL, SPARQL (new)
Item “place of death (P20): Items with this property should also have “place of death (P20)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Item P20, search, SPARQL, SPARQL (new)
Item “date of death (P570): Items with this property should also have “date of death (P570)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Item P570, SPARQL, SPARQL (new)
Item “manner of death (P1196): homicide (Q149086), death in battle (Q18663901): Items with this property should also have “manner of death (P1196): homicide (Q149086), death in battle (Q18663901)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Item P1196, search, SPARQL (new)
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Single value, SPARQL, SPARQL (new)
Contemporaries:
if [item A] has this property (killed by (P157)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Contemporary, SPARQL, SPARQL (new)
Contemporaries:
if [item A] has this property (P157) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P157#Contemporary, SPARQL

name and alias[edit]

I think "killed by" is all that is needed. Assassination only applies to prominent victims such as presidents and heads of state, and killed by covers that anyhow. Danrok (talk) 02:57, 27 February 2013 (UTC)

That's why the aliases aren't listed as the label. But we need them there for the convenience of people typing into the claim box, especially since this property had like 5 different suggested names at WD:PP. — PinkAmpers&(Je vous invite à me parler) 18:46, 27 February 2013 (UTC)

Why not suicide?[edit]

I see that people are thinking murder, assassination... but this can work equally well for suicides, can it not, simply by entering the name of the subject for this property? Shawn in Montreal (talk) 02:06, 30 March 2013 (UTC)

I suppose it could work but I'm not a big fan of that idea. Murder and suicide are very distinct things. If people write a query to know the list of people killed by Marilyn Monroe, we should return an empty list. Worse yet, if someone hopes to get the list of victims in the Columbine massacre through the query "people killed by Q2268542", all they're going to get is "Eric Harris and Dylan Klebold". I think that's a pretty bad outcome. Pichpich (talk) 03:44, 30 March 2013 (UTC)
Since Marilyn Monroe killed herself, I don't see why it should return an empty list. But I've stated my argument and won't belabour it. Shawn in Montreal (talk) 03:50, 30 March 2013 (UTC)
I don't know what you mean by the words "murder" and "suicide" that make them very distinct things in your mind, but the label of this property is "killed by", and the very definition of suicide is a person intentionally killing themselves. In other words, "A killed by A" means "A commited suicide". Therefore, we shouldn't return an empty list for the list of people killed by Marilyn Monroe, and I don't see by what reasoning "people killed by Q2268542" would return only "Eric Harris and Dylan Klebold"; it should return their victims as well as themselves. Silver hr (talk) 01:42, 31 March 2013 (UTC)

Use manner of death (P1196) to capture information about suicide. The 'killed by' claim can then trivially be inferred; there's no need to add that kind of redundant information. Emw (talk) 18:46, 7 March 2015 (UTC)

Inverse property and qualifiers for this?[edit]

I am trying to use this property and I notice you can link a victim to his/her murderer, but you can't link back - we need the inverse property, which I will propose. Also, I think we need some qualifiers for the property (by gunshot, by strangulation, etc) Jane023 (talk) 08:22, 3 May 2015 (UTC)

Inventors killed by their own invention[edit]

SELECT ?inventor ?inventorLabel ?gadet ?gadgetLabel
WHERE {
  ?inventor wdt:P157 ?gadget .
  ?gadet wdt:P61 ?inventor .
  SERVICE wikibase:label {
    bd:serviceParam wikibase:language "en" .
    ?inventor rdfs:label ?inventorLabel .
    ?gadget rdfs:label ?gadgetLabel .
  }
}

Try it! --Tobias1984 (talk) 13:19, 24 June 2016 (UTC)

Extend this property to organizations[edit]

Plenty of times a person is killed by an organization in which there is no identifiable person. Examples include:

I think we should include organization (Q43229) en their subclasses as valid values for this property.--Zeroth (talk) 01:55, 21 August 2018 (UTC)

✓ Done. here.--Zeroth (talk) 21:17, 31 May 2019 (UTC)