Property talk:P1278

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Legal Entity Identifier
identifier for a legally distinct entity per ISO 17442

Description	Uniquely identifies a legally distinct entity. Conforms to the ISO 17442 standard, “Financial Services - Legal Entity Identifier (LEI).”
Represents	Legal Entity Identifier (Q6517388)
Applicable "stated in" value	Global LEI index (Q55259097)
Data type	External identifier
Domain	organization (Q43229), business (Q4830453), company (Q783794), administrative territorial entity (Q56061), human (Q5) or human settlement (Q486972)
Allowed values	[0-9A-Z]{18}[0-9]{2} (20-digit, alpha-numeric string)
Example	ExxonMobil (Q156238) → J3WHBG0MTS7O8ZVMDC91 (RDF) MakoLab (Q16574093) → 2594007XIACKNMUAW223 (RDF) Australian Red Cross (Q4824610) → 549300KKOL7XWW37TS60 (RDF) Central Bank of Egypt (Q920699) → QPLH1J8M7Y52YWI9GF53 (RDF)
Source	https://openleis.com/ https://lei.info https://www.gleif.org/en/
Formatter URL	https://search.gleif.org/#/record/$1
Robot and gadget jobs	Bots could populate a great deal of LEIs for corporations/companies.
See also	ISO 9362 SWIFT/BIC code (P2627), ISIN (P946)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Mix'n'match (Report) Database reports/Complex constraint violations/P1278 Database reports/Constraint violations/P1278 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 53,983 Main statement 51,864 out of 1,439,460 (4% complete) 96.1% of uses Qualifier 4 <0.1% of uses Reference 2,115 3.9% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “[0-9A-Z]{18}[0-9]{2}”: value must be formatted using this pattern (PCRE syntax). (Help)

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, 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/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

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

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?

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)