Property talk:P570
Documentation
Please remove the following deprecated parameters: proposed by.
- Start a query
- Current uses
- With precision and calendarmodel
- Statistics by class
- By century
- Date precision
- Calendar models
- List of qualifiers
- Count
date on which the subject died
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
List of violations of this constraint: Database reports/Constraint violations/P570#Type Q5, Q95074, Q7239, Q215627, Q13002315, Q16334295, Q21070568, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#Conflicts with P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#Range
List of violations of this constraint: Database reports/Constraint violations/P570#single best value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#citation needed
List of violations of this constraint: Database reports/Constraint violations/P570#Entity types
List of violations of this constraint: Database reports/Constraint violations/P570#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#Item P569, SPARQL
![]() |
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
List of violations of this constraint: Database reports/Constraint violations/P570#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#Type Q5, Q95074, Q144, Q726, Q146, Q33602, Q36611, Q80174, Q7378, Q4126704, Q33609, Q26843, Q193327, Q19537, Q36341, Q133006, Q41050, Q237260, Q34505
List of violations of this constraint: Database reports/Constraint violations/P570#Item P21, SPARQL. Count by value
List of violations of this constraint: Database reports/Constraint violations/P570#Item P19, SPARQL. Count by value
List of violations of this constraint: Database reports/Constraint violations/P570#Item P569, SPARQL. Count by value
List of violations of this constraint: Database reports/Constraint violations/P570#Item P20, SPARQL. Count by value
List of violations of this constraint: Database reports/Constraint violations/P570#Qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P570#Conflicts with
![](http://upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
People died before 1582 who's death date is registered using proleptic Gregorian calendar (Q1985727) instead of proleptic Julian calendar (Q1985786). (Help)
Violations query:
SELECT ?item WHERE { ?item p:P570/psv:P570 ?datevalue . ?datevalue wikibase:timeValue ?date . FILTER(?date < "+1582-10-15T00:00:00Z"^^xsd:dateTime) ?datevalue wikibase:timePrecision ?dateprecision . FILTER(?dateprecision > 9) ?datevalue wikibase:timeCalendarModel wd:Q1985727 . } LIMIT 1000
List of this constraint violations: Database reports/Complex constraint violations/P570#Wrong calendar
Experimental constraints (partial)
If subject has an item as their mother (mother (P25)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their spouse (spouse (P26)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their country (country of citizenship (P27)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their country (country of citizenship (P27)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their sports team (member of sports team (P54)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their sports team (member of sports team (P54)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their ancestral home (ancestral home (P66)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their ancestral home (ancestral home (P66)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject was educated at (educated at (P69)) an item, subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject was educated at (educated at (P69)) an item, subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
member of political party (P102):
If subject has an item as their political party (member of political party (P102)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their political party (member of political party (P102)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their employer (employer (P108)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their employer (employer (P108)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their league (league (P118)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their league (league (P118)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their movement (movement (P135)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their movement (movement (P135)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their religion (religion or worldview (P140)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their religion (religion or worldview (P140)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject was killed by (killed by (P157)) an item, subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their doctoral advisor (doctoral advisor (P184)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their doctoral student (doctoral student (P185)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their head coach (head coach (P286)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their military rank (military rank (P410)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their military rank (military rank (P410)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their astronaut mission (astronaut mission (P450)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their astronaut mission (astronaut mission (P450)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their partner (unmarried partner (P451)), subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject is member of (member of (P463)) an item, subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject is member of (member of (P463)) an item, subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their chivalric order (chivalric order (P550)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their chivalric order (chivalric order (P550)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their residence (residence (P551)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their residence (residence (P551)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
commander of (DEPRECATED) (P598):
If subject is commander of (commander of (DEPRECATED) (P598)) an item, subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject is commander of (commander of (DEPRECATED) (P598)) an item, subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their conflict (conflict (P607)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their conflict (conflict (P607)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their religious order (religious order (P611)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their religious order (religious order (P611)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their sport (sport (P641)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their sport (sport (P641)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject was drafted by (drafted by (P647)) an item, subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject was drafted by (drafted by (P647)) an item, subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject is student of (student of (P1066)) an item, subject death's date should be after the linked item was born (date of birth (P569)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their affiliation (affiliation (P1416)), subject death's date should be after the linked item was founded or created (inception (P571)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
If subject has an item as their affiliation (affiliation (P1416)), subject death's date should be after the linked item started (start time (P580)).
List of violations of this constraint: Database reports/Constraint violations/P570#Diff within range
![]() | Graphs are temporarily unavailable due to technical issues. |
|
Keeping up to date
As one of the major uses of Wikidata is to keep Wikipedias up to to date, I thought it could be worth trying to organize things a bit. I found http://www.legacy.com/memorial-sites/2014/ that allows to keep watch of the recently dead. Could also do something like a "dead this week list that Wikipedias could consult ? --Zolo (talk) 09:28, 12 April 2014 (UTC)
Died "after 1110"
According to William Devereux, he died "after 1110". Is there a way to add it with date of death (P570) at William Devereux (Q8007795)? --- Jura 12:37, 17 May 2014 (UTC)
- He died before 1210 for sure. May be to point date of death (P570) = 1160±50? --Infovarius (talk) 10:11, 23 May 2014 (UTC)
- In the meantime, there is the property "floruit": I added that.
- The article also mentions the he was likely dead a some point "During the time of Abbot William (1113 to 1130)". I tried to include this with the two other new properties: P1319 and P1326 --- Jura 16:52, 24 May 2014 (UTC)
Living people and no value
All people die at some point in time. Did we already had a discussion somewhere about adding no value to living people? We could be a bit more philosophical and add "unknown value" (everyone dies, we just don't know when), but that would make it harder to distinguish with people we do know they died, just not sure when. Multichill (talk) 19:52, 8 October 2014 (UTC)
- I prefer to use "unknown value" for peoples with unknown death date only. "no value" is applicable for god and some other fictional characters maybe. I think it is better do not create this property for living peoples at all. If we will create this property, will we add place of death (P20)='no value', place of burial (P119)='no value', image of grave (P1442)='no value', cause of death (P509)='no value', manner of death (P1196)='no value', killed by (P157)='no value' to all living peoples too? — Ivan A. Krestinin (talk) 21:09, 8 October 2014 (UTC)
- strong
Support--Oursana (talk) 22:24, 8 October 2014 (UTC)
- "unknown value" seems indeed confusinhg, but we seem to need a way to say "this person is not dead this is why we do not provide a death date (equivalent to Category:Living people (Q5312304) for Wikipedia).
- Even though it is conceptually shaky, I guess "no vaue" is the most practical solution. We could have a common sense guideline saying: "if someone is not dead (and has no definite, sourceable death forecasts), add "date of death: no value", do not add other properties like place of death, etc.". --Zolo (talk) 07:39, 9 October 2014 (UTC)
Oppose for living people this field shall stay untouched. It would be filled someday anyway. So far we have no difference in wikipedia infoboxes in "no value at all" and "empty value", and filling this field basing on categories is very very bad idea. Thus i see no reason to confuse data clients. -- Vlsergey (talk) 08:01, 9 October 2014 (UTC)
- I was not suggesting to add it based on categories (though I do not see major issues doing that as a first step). My point was that these "not dead people" categories exist (I think partly articles about living people are more sensitive, and partly because it is a useful marker for maintenance), and if we want to have the same information on Wikidata, the simplest solution seems to go through "unknown values". Well admittedly, we can probably also do without adding anything and find other ways to check for missing death dates. --Zolo (talk) 14:18, 9 October 2014 (UTC)
- The reason I brought this up here is because I talked with Daniel about this last weekend. I just want to see what according to you guys, the pro's and con's are. The mass adding would maybe be a next step, but let's just leave that part for later. Please don't make this a sliding scale argument. Introducing something like this only makes sense when we're ready for it and when it doesn't mean we'll create a huge backlog because the data isn't available.
- The pro is that it's easier to track completeness. Every human should just have the property. Easy to do reports and fix things.
- The con is maybe the extra work and that downstream (Wikipedia) will get confused.
- Multichill (talk) 12:25, 11 October 2014 (UTC)
- I was not suggesting to add it based on categories (though I do not see major issues doing that as a first step). My point was that these "not dead people" categories exist (I think partly articles about living people are more sensitive, and partly because it is a useful marker for maintenance), and if we want to have the same information on Wikidata, the simplest solution seems to go through "unknown values". Well admittedly, we can probably also do without adding anything and find other ways to check for missing death dates. --Zolo (talk) 14:18, 9 October 2014 (UTC)
- Albeit a little bit late, I am adding my comment as I could not work out if any conclusion was reached above and I have a vested interest in utilising birth and death dates. We should be working on the assumption that the person is alive unless we know otherwise. i.e. We do not add any death related properties until that person is > 125 years old or that we know for fact that they died. Only then we can use the "date of death = unknown" option.
- If a date of death property is added to everyone "in anticipation", then we cannot distinguish those who are known to have died but we are just missing a date. Periglio (talk) 09:34, 24 January 2015 (UTC)
- I think it´s a good idea to use "no value" for gods and/or fictional persons who don´t die (or can´t die). There will for sure be no value ever. For persons that are definitely not alive any more but the date of death is unknown it is good to use "unknown value" (e.g. birth date is before 1900 or has published works before 1920). Unknown value implies there is a value we don´t know today. There might be a yet unidentified source out there, that can provide the value some day. For living persons we should ommit the property at all.--Giftzwerg 88 (talk) 15:49, 24 January 2015 (UTC)
- For living people, there is also floruit (P1317). It can include a date and a reference. --- Jura 20:05, 5 May 2015 (UTC)
- I think it´s a good idea to use "no value" for gods and/or fictional persons who don´t die (or can´t die). There will for sure be no value ever. For persons that are definitely not alive any more but the date of death is unknown it is good to use "unknown value" (e.g. birth date is before 1900 or has published works before 1920). Unknown value implies there is a value we don´t know today. There might be a yet unidentified source out there, that can provide the value some day. For living persons we should ommit the property at all.--Giftzwerg 88 (talk) 15:49, 24 January 2015 (UTC)
Dates available at Wikipedia
At frwiki, I added a maintenance category for P570: fr:Catégorie:P570 absent de Wikidata. Currently just one or two templates feed into that. --- Jura 10:42, 16 June 2015 (UTC)
Death during the night ?
Hello, I came across Jean-Yves Cozan (Q3170127) for who the sources say he is dead during the night between the 15th and 16th June, is there any way to code that in WD ? 20:22, 16 June 2015 (UTC)
- Hi, data model have ability to describe this case. But current Wikidata core and editor implementation does not support required model features. — Ivan A. Krestinin (talk) 22:49, 16 June 2015 (UTC)
Declared dead
At Q3517088#P570, I added as qualifier declared dead (Q21091870). Not sure if the date should be in 1984 or 2004. --- Jura 11:56, 12 October 2015 (UTC)
- @Jura1: I don't know, but I think I would personally use sourcing circumstances (P1480) as the property of the qualifier for that case... -- Agabi10 (talk) 18:28, 12 October 2015 (UTC)
- Not sure about the use of that qualifier. It might make sense on the date in 1984.
- The problem is that it's a theoretical date. Here is another one: Q5577585#P570.--- Jura 16:37, 14 October 2015 (UTC)
Value for reason for deprecated rank (P2241)
person found to be alive (Q21124171) can be used. --- Jura 11:48, 16 October 2015 (UTC)
BCE / BC
This (and I guess other dates) support the BCE format e.g. https://www.wikidata.org/wiki/Q317947 BCE 285 which differ from en.wikipedia 285 BC. This affects the connectivity between these two. Can it supports the BC format as well? הנדב הנכון (talk) 07:49, 20 June 2016 (UTC)
- All Properties
- Properties with time-datatype
- Properties used on 1000000+ items
- Properties with difference within range constraints
- Properties with constraints on type
- Properties with qualifiers constraints
- Properties with conflicts with constraints
- Properties with range constraints
- Properties with single best value constraints
- Properties with citation needed constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with constraints on items using them
- Properties using constraint templates
- Properties with complex constraints
- Person properties