Property talk:P1376
Latest comment: 2 years ago by Fantastoria in topic Fictional locations
Documentation
capital of
country, state, department, canton or other administrative division of which the municipality is the governmental seat
country, state, department, canton or other administrative division of which the municipality is the governmental seat
Represents | administrative centre (Q1306755) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | Item | ||||||||||||
Example | Niamey (Q3674) → Niger (Q1032) Berlin (Q64) → Germany (Q183) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P1376 (Q23908994) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
Inverse property of “capital (P36)”:
if [item A] has this property (capital of (P1376)) linked to [item B],
then [item B] should also have property “capital (P36)” linked to [item A]. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (capital of (P1376)) linked to [item B],
then [item B] should also have property “capital (P36)” linked to [item A]. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1376#inverse, 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/P1376#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1376#Item P17, search, SPARQL
Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Singapore (Q334)List of violations of this constraint: Database reports/Constraint violations/P1376#Item P131, search, SPARQL
Item “coordinate location (P625)”: Items with this property should also have “coordinate location (P625)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Veligrad (Q1131299), fictional city (Q1964689)List of violations of this constraint: Database reports/Constraint violations/P1376#Item P625, SPARQL
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Condate Riedonum (Q16507528), Lugdunum (Q665), Veligrad (Q1131299), fictional city (Q1964689), Messantia (Q5703763), Tarantia (Q107665069)
List of violations of this constraint: Database reports/Constraint violations/P1376#Item P1566, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1376#Item P1566, search, SPARQL
Conflicts with “instance of (P31): human (Q5), Wikimedia category (Q4167836), Wikimedia disambiguation page (Q4167410), organization (Q43229), book (Q571), encyclopedia article (Q13433827), comarca of Galicia (Q5150550)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1376#Conflicts with P31, hourly updated report, SPARQLContemporaries:
if [item A] has this property (capital of (P1376)) 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. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (capital of (P1376)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1376#Contemporary, SPARQL
Value type “administrative territorial entity (Q56061), fictional administrative territorial entity (Q64034456), fictional geographic region (Q20750954), island (Q23442), urban area (Q702492)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value administrative territorial entity (Q56061), fictional administrative territorial entity (Q64034456), fictional geographic region (Q20750954), island (Q23442), urban area (Q702492) (or a subclass thereof). (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/P1376#Value type Q56061, Q64034456, Q20750954, Q23442, Q702492, 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/P1376#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/P1376#Scope, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Values completed based on capital (P36)
editWith this, I added missing capital of (P1376) to items. "Stated in" indicates the item where P36 was found. If capital of (P1376) is incorrect and has to be removed, that other item needs to be corrected as well. --- Jura 10:30, 7 July 2015 (UTC)
Fictional locations
editIs there a way to put a general exception for fictional locations to item-requires-statement constraint with coordinate location and GeoNames ID values? Thanks. --Fantastoria (talk) 09:22, 18 August 2022 (UTC)