Property talk:P1278
Jump to navigation
Jump to search
Documentation
Legal Entity Identifier
identifier for a legally distinct entity per ISO 17442
identifier for a legally distinct entity per ISO 17442
[create Create a translatable help page (preferably in English) for this property to be included here]
List of violations of this constraint: Database reports/Constraint violations/P1278#Format, hourly updated report, SPARQL
Type “organization (Q43229), business (Q4830453), company (Q783794), administrative territorial entity (Q56061), human (Q5), human settlement (Q486972)”: item must contain property “instance of (P31)” with classes “organization (Q43229), business (Q4830453), company (Q783794), administrative territorial entity (Q56061), human (Q5), human settlement (Q486972)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Dulaney Valley Memorial Gardens (Q5313294)List of violations of this constraint: Database reports/Constraint violations/P1278#Type Q43229, Q4830453, Q783794, Q56061, Q5, Q486972, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1278#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)Single value: this property generally contains a single value. (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/P1278#Single value, SPARQL
Conflicts with “country (P17): Algeria (Q262)”: this property must not be used with the listed properties and values. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Bank of Algeria (Q1774622)List of violations of this constraint: Database reports/Constraint violations/P1278#Conflicts with P17, search, SPARQL
Conflicts with “country (P17): Mauritania (Q1025)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1278#Conflicts with P17, hourly updated report, search, SPARQLAllowed 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/P1278#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): 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/P1278#Scope, SPARQL
![](http://178.128.105.246/cars-http-upload.wikimedia.org/wikipedia/commons/thumb/a/a6/Pictogram_voting_comment.svg/40px-Pictogram_voting_comment.svg.png)
LOU code 5493, 3157, 5493, 9695, 9884
For these LOUs, the two chars in pos 5-6 should be "00" (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P1278#LOU code 5493, 3157, 5493, 9695, 9884
For these LOUs, the two chars in pos 5-6 should be "00" (Help)
Violations query:
SELECT ?item ?value { ?item wdt:P1278 ?value . FILTER (substr(?value,1,4) in ("5493","3157","5493","9695","9884") && !substr(?value,5,2) = "00") }
List of this constraint violations: Database reports/Complex constraint violations/P1278#LOU code 5493, 3157, 5493, 9695, 9884
![]() |
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
URL
[edit]URL of this property should be https://www.gleif.org/lei/$1
gleif.org is the official organisation which manages legal entity identifiers.
What happens to reassigned LEIs?
[edit]LEIs can be reassigned, e.g. 549300LKT9PW7ZIBDF31 which used to belong to Fiat Chrysler Automobiles but now belongs to Stellantis. This violates the distinct-values constraint. Should the LEI be removed from the old item, or left but with an end date? AFAIK an end date wouldn't resolve the distinct-values constraint violation. FrozenRabbitHole (talk) 12:27, 15 August 2023 (UTC)
- It's still the same entity, Fiat Chrysler Automobiles NV became Stellantis NV on 2021-01-19 by means of renaming the company. LEIs are unique. If you want to distinguish the "old" entity and the "new" one then yes, one of them has to give. I'd say put the LEI on Q97439162 and manage the link between these resources via Property:P1365. Hroptatyr (talk) Hroptatyr (talk) 01:51, 16 August 2023 (UTC)
Categories:
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with format constraints
- Properties with constraints on type
- Properties with unique value constraints
- Properties with single value constraints
- Properties with conflicts with constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with complex constraints