Property talk:P509

From Wikidata
Jump to navigation Jump to search

Documentation

cause of death
underlying or immediate cause of death. Underlying cause (e.g. car accident, stomach cancer) preferred. Use 'manner of death' (P1196) for broadest category, e.g. natural causes, accident, homicide, suicide
Representscause of death (Q1931388)
Data typeItem
Template parameter"death_cause" in en:Template:Infobox person - see Template:Infobox person (Q6249834)
Domainperson (Q215627), organism (Q7239), group of living things (Q16334298), character that may or may not be fictional (Q21070598), group of fictional characters (Q14514600) or fictional character (Q95074)
ExampleAlexander Radishchev (Q217470)nitric acid poisoning (Q21639963)
Richard Nixon (Q9588)stroke (Q12202)
Agrafena Saburova (Q4403616)cholera (Q12090)
Theodore Roosevelt (Q33866)coronary thrombosis (Q707774)
Adolf Hitler (Q352)shot to the head (Q15824243)
Heinrich Himmler (Q43067)cyanide poisoning (Q883082)
Adolf Eichmann (Q28085)hanging (Q175111)
Albert Fish (Q507748)electrocution (Q3587621)
John Wayne Gacy (Q298252)lethal injection (Q210035)
congestive heart failure (Q19000661)
Maximilian Kolbe (Q153850)asphyxia (Q193840)
Wilt Chamberlain (Q182455)congestive heart failure (Q19000661)
Lou Gehrig (Q357444)amyotrophic lateral sclerosis (Q206901)
Paul Walker (Q213864)traffic collision (Q9687)
Natalie Wood (Q180919)drowning (Q506616)
Jeffrey Dahmer (Q298364)cranial trauma (Q2920572)
blunt trauma (Q770709)
John Lennon (Q1203)ballistic trauma (Q2140674)
Michiel de Ruyter (Q316945)wounded in action (Q2603108)
Lillian Leitzel (Q6548159)falling from height (Q11637534)
Andy Kaufman (Q299983)cancer (Q12078)
Sourceen:Category:Deaths by cause (note: this information should be moved to a property statement; use property source website for the property (P1896))
Robot and gadget jobsDeltaBot does the following jobs:
Tracking: sameno label (Q42533437)
Tracking: usageCategory:Pages using Wikidata property P509 (Q22913695)
See alsomanner of death (P1196), military casualty classification (P1347), cause of destruction (P770)
Lists
  • Items with the most statements of this property
  • Count of items by number of statements (chart)
  • Count of items by number of sitelinks (chart)
  • Items with the most identifier properties
  • By value of property
  • Items with no other statements
  • Most recently created items
  • Items with novalue claims
  • Items with unknown value claims
  • Usage history (total)
  • Chart by item creation date
  • Map of people by place values:
  • January 1st dates
  • Database reports/Constraint violations/P509
  • Map
  • Random list
  • Proposal discussionProposal discussion
    Current uses
    Total140,786
    Main statement138,15298.1% of uses
    Qualifier2,6051.9% of uses
    Reference29<0.1% of uses
    Search for values
    [create Create a translatable help page (preferably in English) for this property to be included here]
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Type Q215627, Q7239, Q16334298, Q21070598, Q14514600, Q95074, SPARQL
    Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Item P21, search, SPARQL
    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. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Item P570, SPARQL
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#none of, SPARQL
    Citation needed: the property must have at least one reference (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#citation needed
    Item “manner of death (P1196): Items with this property should also have “manner of death (P1196)”. (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Item P1196, search, SPARQL
    Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Entity types
    Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#Scope, SPARQL
    None of gunshot (Q2992372): value must not be any of the specified items.
    Replacement property:
    Replacement values: ballistic trauma (Q2140674) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#none of, SPARQL
    None of headshot (Q1332264): value must not be any of the specified items.
    Replacement property:
    Replacement values: shot to the head (Q15824243) (Help)
    Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
    List of violations of this constraint: Database reports/Constraint violations/P509#none of, SPARQL
    Value electric chair (Q185639) will be automatically replaced to value electrocution (Q3587621).
    Testing: TODO list
    Value execution by hanging (Q11608124) will be automatically replaced to value hanging (Q175111).
    Testing: TODO list
    Value execution by firing squad (Q216169) will be automatically replaced to value ballistic trauma (Q2140674).
    Testing: TODO list
    Value guillotine (Q128015) will be automatically replaced to value decapitation by guillotine (Q56649284).
    Testing: TODO list
    Value gas chamber (Q205348) will be automatically replaced to value asphyxia (Q193840).
    Testing: TODO list
    Value suicide by hanging (Q7883956) will be automatically replaced to value hanging (Q175111).
    Testing: TODO list
    Value suicide by shooting (Q39917302) will be automatically replaced to value ballistic trauma (Q2140674).
    Testing: TODO list
    Value natural causes (Q3739104) will be automatically replaced to value natural causes (Q3739104) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value accident (Q171558) will be automatically replaced to value accidental death (Q21142718) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value accidental death (Q21142718) will be automatically replaced to value accidental death (Q21142718) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value suicide (Q10737) will be automatically replaced to value suicide (Q10737) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value murder (Q132821) will be automatically replaced to value homicide (Q149086) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value homicide (Q149086) will be automatically replaced to value homicide (Q149086) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value unnatural death (Q855919) will be automatically replaced to value unnatural death (Q855919) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value pending investigation (Q15729048) will be automatically replaced to value pending investigation (Q15729048) and moved to manner of death (P1196) property.
    Testing: TODO list
    Value capital punishment (Q8454) will be automatically replaced to value capital punishment (Q8454) and moved to manner of death (P1196) property.
    Testing: TODO list
    If property value equals to cancer (Q12078) then claim manner of death (P1196) = natural causes (Q3739104) will be created automatically.
    Testing: TODO list
    If property value equals to tuberculosis (Q12204) then claim manner of death (P1196) = natural causes (Q3739104) will be created automatically.
    Testing: TODO list
    Value gunshot (Q2992372) will be automatically replaced to value ballistic trauma (Q2140674).
    Testing: TODO list
    Value fall (Q11620540) will be automatically replaced to value falling from height (Q11637534).
    Testing: TODO list
    Value COVID-19 pandemic (Q81068910) will be automatically replaced to value COVID-19 (Q84263196).
    Testing: TODO list
    This property is being used by:

    Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

    Property proposal discussions[edit]

    Values[edit]

    Currently the property combines a few different concepts in my opinion. That means that we potentially can increase the data structure. Some subgroups I noticed are:

    • Diseases
    • Life ending methods (e.g. decapitation, stoning)
    • Circumstances of death (e.g. accident, assassination, plane crash, duel)
    • Life ending tools (e.g. shell (Q318028), land mine)

    We could also add the details into the qualifier:

    • Cause of death: murder
    • circumstance of death: robbery
    • life ending device: gun
    • life ending trauma: gunshot wound

    or

    • Cause of death: disease
    • circumstance of death: contracted disease
    • disease: malaria
    • life ending trauma: multiple organ failure

    Examples are not well thought out, but its just something to think about for the future. --Tobias1984 (talk) 13:22, 2 December 2013 (UTC)[reply]

    @Emw: Can you take a look at this the next time you have time? --Tobias1984 (talk) 15:40, 21 January 2014 (UTC)[reply]
    I agree, this one has become messy. Murder is not a cause of death. There's some causes on this page: List of causes of death by rate. A new property such as circumstances of death may be useful for claiming some on was murdered, etc. Danrok (talk) 01:25, 4 February 2014 (UTC)[reply]
    @Danrok, Emw: I think Emw would suggest that the new property should be independent (and not a qualifier as in my example above). --Tobias1984 (talk) 12:27, 4 February 2014 (UTC)[reply]
    @Tobias1984, Emw: Proposal here: Wikidata:Property_proposal/Person#circumstances_of_death. Danrok (talk) 17:27, 5 February 2014 (UTC)[reply]

    Single value?[edit]

    It is quite common that a death has several causes, see for example Henrik Ibsen. Jeblad (talk) 10:07, 24 July 2015 (UTC)[reply]

    Some improvements[edit]

    I propose to change

    ⟨ subject ⟩ cause of death (P509) View with SQID ⟨ execution by firing squad (Q216169)  View with Reasonator View with SQID ⟩

    with

    ⟨ subject ⟩ cause of death (P509) View with SQID ⟨ ballistic trauma (Q2140674)  View with Reasonator View with SQID ⟩

    (may be to add something about Q216169 (manner of death (P1196)?). And I feel that values Armenian genocide (Q80034), Smolensk air disaster (Q131311) should be changed somehow but I can't propose with what. --Infovarius (talk) 07:30, 19 June 2018 (UTC)[reply]

    Hm, but this is a loss of information. How to keep ballistic trauma (Q2140674)? --Infovarius (talk) 15:46, 15 December 2021 (UTC)[reply]

    Date of birth necessary?[edit]

    It says "An entity with cause of death should also have a statement date of birth." Why? This means that a person of who the date of birth is unknown, which isn't uncommon for persons who lived in the Middle Ages, cannot have a cause of death? Weird... --HRvO (talk) 09:53, 19 August 2018 (UTC)[reply]

    @HRvO: I'm not sure why that would be specified. It might mean that it's preferable, but not mandatory. - Bossanoven ( talk) 11:46, 19 August 2018 (UTC)[reply]
    I'm also getting this warning, while editing the item for a person whose date of birth is unknown. Date of birth is unrelated to cause of death. This should not be a constraint. --Infomuse (talk) 01:54, 18 November 2018 (UTC)[reply]
    If the date of birth is unknown, there should be a date of birth statement with a value of "unknown". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:46, 1 June 2020 (UTC)[reply]
    It makes no sense at all adding birth dates with "unknown" value just to avoid a warning that shouldn't be there in first place. Therefore, I was bold and removed it.--DarwIn (talk) 04:07, 16 December 2020 (UTC)[reply]

    Need constraint to prevent it from being used in places like mechlorethamine exposure (Q21513721)[edit]

    Currently cause of death (P509) is used incorrectly on mechlorethamine exposure (Q21513721) - this should be prevented by a constraint.

    Single value constraint[edit]

    We should remove the single value constraint. In the UK, for example, it is usual to have up to three causes on a death certificate. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:45, 1 June 2020 (UTC)[reply]

    Killed in Action[edit]

    killed in action (Q210392) doesn't belong here. It should be recorded as manner of death (P1196)death in battle (Q18663901) and military casualty classification (P1347)killed in action (Q210392). (And I would additionally merge those values or killed in action (Q210392)subclass of (P279)death in battle (Q18663901), but that's less clear) --Matthias Winkelmann (talk) 18:08, 10 October 2020 (UTC)[reply]

    Fictional Characters[edit]

    Is there a way to remove the date of death constraint for fictional characters? Koziarke (talk) 16:29, 11 December 2022 (UTC)[reply]