Property talk:P171
Documentation
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:
When possible, data should only be stored as statementstaxon (Q16521) | ||||||||||||||||
| Allowed values | taxon (Q16521) (note: this should be moved to the property statements) | ||||||||||||||||
| Example | Homo sapiens (Q15978631) → Homo (Q171283) Matricaria chamomilla (Q28437) → Matricaria (Q27618) Thermodesulfobacteriaceae (Q1151561) → Thermodesulfobacteriales (Q20643849) SARSr-CoV (Q278567) → Sarbecovirus (Q57754693) | ||||||||||||||||
| Tracking: usage | Category:Pages using Wikidata property P171 (Q27968952) | ||||||||||||||||
| Lists |
| ||||||||||||||||
| Proposal discussion | Proposal discussion | ||||||||||||||||
| Current uses |
| ||||||||||||||||
| Search for values |
List of violations of this constraint: Database reports/Constraint violations/P171#Type Q16521, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P171#Item P225, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P171#Item P105, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P171#Entity types
List of violations of this constraint: Database reports/Constraint violations/P171#Scope, SPARQL
Ichnogenera are defined by the morphology of traces produced by organisms rather than organism morphology and does not involve parent ranks above the binomial nomenclature for ichnotaxa. (Help)
Violations query:
SELECT DISTINCT ?item ?itemLabel WHERE { SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE]". } { SELECT DISTINCT ?item WHERE { { ?item p:P105 ?statement0. ?statement0 ps:P105 wd:Q112082101. } UNION { ?item p:P31 ?statement1. ?statement1 ps:P31 wd:Q112082101. } ?item p:P171 ?statement2. ?statement2 (ps:P171/(wdt:P171*)) _:anyValueP171. } } }List of this constraint violations: Database reports/Complex constraint violations/P171#parent taxon unsuited for ichnogenus
Retains generic constraint requiring a parent taxon on taxon items for items which do not represent ichnogenera. (Help)
Violations query:
SELECT DISTINCT ?item ?itemLabel WHERE { SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE]". } { SELECT DISTINCT ?item WHERE { ?item wikibase:sitelinks _:anyValue. MINUS { ?item p:P171 ?statement0. ?statement0 (ps:P171/(wdt:P171*)) _:anyValueP171. } MINUS { ?item p:P105 ?statement1. ?statement1 (ps:P105) ?instance. } MINUS { ?item (p:P105/ps:P105) wd:Q112082101. } } } }List of this constraint violations: Database reports/Complex constraint violations/P171#taxon without parent taxon and rank other than ichnogenus
| ||||||||||||||||||||||||||||||
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)
- Whew, an answer! Thanks. Espeso (talk) 21:39, 2 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
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
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
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)
Acceptable sources/references edit
This is mostly related to discussion here.
Should values here be only from other taxonomic databases (i.e. scientific articles alone is not sufficient for a source), and if so which ones and can we add this guideline to this property description or usage instructions?
(CC: @Christian_Ferrer:)
fictional taxa edit
@succu: You said this property is not appropriate for taxa from fiction, and so I wonder 1) why not? and 2) what property might be used instead...P279? Arlo Barnes (talk) 18:44, 1 December 2019 (UTC)