Property talk:P171

From Wikidata
Jump to: navigation, search

Documentation

parent taxon
closest parent taxon of the taxon in question
Description next higher taxon according to a certain taxonomic viewpoint. As multiple taxonomic viewpoints exist, more than one parent taxon is possible.
Represents taxon (Q16521)
Data type Item
Domain
According to this template: taxon (Q16521)
According to statements in the property:
taxon (Q16521)
When possible, data should only be stored as statements
Allowed values taxon (Q16521) (note: this should be moved to the property statements)
Example dog (Q144)Canis lupus (Q18498)
domestic pig (Q787)Sus scrofa (Q58697)
plant (Q756)Eukaryote (Q19088)
butterfly (Q11946202)Lepidoptera (Q28319)
Common Raven (Q25357)Corvus (Q43365)
Tracking: usage Category:Pages using Wikidata property P171 (Q27968952)
Lists
Proposal discussion Property proposal/Archive/2#P171
Current uses 2,355,821
[create] Create a translatable help page (preferably in English) for this property to be included here
Type “taxon (Q16521): element must contain property “instance of (P31)” with classes “taxon (Q16521)” or their subclasses (defined using subclass of (P279)).
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P171#Type Q16521, SPARQL
Item “taxon name (P225): Items with this property should also have “taxon name (P225)”.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P171#Item P225, SPARQL
Item “taxon rank (P105): Items with this property should also have “taxon rank (P105)”.
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P171#Item P105, SPARQL
Property “parent taxon (P171)” declared by target items of “parent taxon (P171): If [item A] has this property with value [item B], [item B] is required to have property “parent taxon (P171)”.
Exceptions are possible as rare values may exist. Known exceptions: biota (Q2382443)
List of this constraint violations: Database reports/Constraint violations/P171#Target required claim P171, SPARQL, SPARQL (by value)



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

Clarification required[edit]

If the parent of genus Foois is family "Fooaceae", then will item "Foois" have both "family: Fooaceae" and "parent taxon: Fooaceae"? Espeso (talk) 15:58, 1 March 2013 (UTC)

Yes, unless there's a tribe "Fooini" in the middle. Then Foois will have parent taxon "Fooini" which in turn has parent taxon "Fooaceae". For a real life example, go to Pterygoplichthys joselimaianus and follow the parent taxons from there all the way to the eukaryotes. Remember to count the clicks. ;) That is the main advantage of this property IMO: It supports cladistics and can be as fine-grained as it needs to be. - Soulkeeper (talk) 21:05, 2 March 2013 (UTC)
Whew, an answer! Thanks. Espeso (talk) 21:39, 2 March 2013 (UTC)
By the way, as long as both this property and taxon rank have values, the taxon rank related properties, e.g. genus, family, order etc., can easily be deduced from them. - Soulkeeper (talk) 00:33, 3 March 2013 (UTC)

Request for deletion[edit]

This property has been nominated for deletion at Wikidata:Requests_for_deletions#Property:P171. Emw (talk) 17:15, 24 March 2013 (UTC)

Debate is now archived at Wikidata:Requests_for_deletions/Archive/2013/04/02#Property:P171. --  Docu  at 16:58, 7 April 2013 (UTC)

Practical[edit]

This is one of the properties where a solid reference for the taxonomic viewpoint that is being put in is very important. This should be a taxonomic reference (not ITIS, CoL, etc, and certainly not an "imported from a Wikipedia"). In practice, it is all right to put in genus, family and order without a reference as a temporary measure, but these should then not be taken seriously. Adding other ranks (subfamily, tribe, etc) without a solid taxonomic reference can only lead to bad results and should be avoided at all times. - Brya (talk) 10:59, 1 October 2014 (UTC)

Reverts about subproperty of subclass of.[edit]

I don't understand the reverts. And I don't want any edit war, so we will have to solve this another way. Any discussion possible ? TomT0m (talk) 19:20, 15 March 2015 (UTC)

Additional constraint[edit]

As stated in this discussion this property can no longer be used in queries like ?item (wdt:P171)* wd:Q756 . where you are looking for items with lower taxa than some item. The issue is timeouts and the suspected culprit, proposed by User:Hoo man), were cycles in the graph, or situation where an item is a parent of an ancestor. One way to look for such items is to find child items whose parent taxon has lower rank than the child item. I think the query below expresses that

SELECT ?item  
{
    ?item  wdt:P171  ?pItem . # parent taxon
    ?item  wdt:P105  ?rank  . # child's rank
    ?pItem wdt:P105  ?pRank . # parent's rank
    ?pRank wdt:P361+ ?rank  . # parent's rank is lower than child's rank
}
limit 10

Try it!

Unfortunately it times out as well. Anybody knows how to fix it? Queries like

SELECT ?item  
{
    ?item  wdt:P171  ?pItem    . # parent taxon
    ?item  wdt:P105  wd:Q34740 . # child rank
    ?pItem wdt:P105  wd:Q7432  . # parent rank
}
limit 10

Try it!

or

SELECT ?item  
{
    ?item  wdt:P171  ?pItem    . # parent taxon
    ?item  wdt:P105 wd:Q227936 . # child rank
    ?pItem wdt:P105 wd:Q34740   . # parent rank
}
limit 10

Try it!

are the only ones not timing out and using them I found several items with wrong rank or parent taxon, but it is hard to go through all the combinations. Ideally we could add some query like that to the constraints. Also pinging User:Succu who is working on related tasks. --Jarekt (talk) 14:32, 11 January 2017 (UTC)