# Entity Name Key: `representation.text.entity_name` Non-person named entity: organisation names, product names, venue names, song/movie/book titles, brand names. Distinguished from full\_name by containing business suffixes (Inc, Corp, Ltd), numbers, ampersands, or other non-personal-name patterns. Page: Samples: `The Olive Garden`, `iPhone 15 Pro`, `Game of Thrones`, `Spotify`, `McKinsey & Company`, `Toyota Motor Corp`, `Harvard University`, `Super Bowl LVIII` ## Background ### Origin FineType defines representation.text.entity\_name as a non-person named entity: organisation names, product names, venue names, song, movie and book titles, and brand names.[[1]](https://github.com/meridian-online/finetype/blob/main/labels/definitions_representation.yaml) FineType's definition tells an entity name apart from a full\_name by business suffixes such as Inc, Corp and Ltd, by numbers, by ampersands, or by other patterns that personal names do not have.[[1]](https://github.com/meridian-online/finetype/blob/main/labels/definitions_representation.yaml) In natural-language processing, named-entity recognition locates named entities in unstructured text and classifies them into categories such as person names, organisations and locations.[[2]](https://en.wikipedia.org/wiki/Named-entity_recognition) ### Use Schema.org defines legalName as the official name of an organisation, for example the registered company name.[[3]](https://schema.org/legalName) GLEIF's LEI-CDF 3.1 format records the legal name of each entity in a LegalName element.[[4]](https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format) In LEI-CDF 3.1, an entity in a jurisdiction with more than one legal name, for example in different languages, has its primary legal name in LegalName and its other names in OtherEntityNames.[[4]](https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format) LEI-CDF 3.1 types the legal name as a string in a natural language, with an xml:lang code saying which language is used.[[4]](https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format) LEI-CDF 3.1 keeps ASCII-transliterated (Latin or Romanised) names in a separate TransliteratedOtherEntityNames element.[[4]](https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format) When you match organisations across files, compare against the other and transliterated names as well as the primary legal name, because the spelling a second source uses may be one of those. (Meridian's view) ISO 20275 specifies the elements of an unambiguous scheme to identify the distinct entity legal forms in a jurisdiction.[[5]](https://www.gleif.org/en/lei-data/code-lists/iso-20275-entity-legal-forms-code-list) GLEIF's ELF Code List, in its February 2026 version, lists more than 3,600 entity legal forms across more than 200 jurisdictions.[[5]](https://www.gleif.org/en/lei-data/code-lists/iso-20275-entity-legal-forms-code-list) The ELF Code List gives legal forms in their native language, such as Gesellschaft mit beschränkter Haftung (GmbH) or Société Anonyme (SA).[[5]](https://www.gleif.org/en/lei-data/code-lists/iso-20275-entity-legal-forms-code-list) GLEIF's ELF page warns that a Dutch BV is not a German GmbH and is not a private limited liability company.[[5]](https://www.gleif.org/en/lei-data/code-lists/iso-20275-entity-legal-forms-code-list) Keep entity names as text exactly as received, with their leading articles, ampersands, numerals and odd capitalisation, and do any normalising in a separate matching column. (Meridian's view) ### Where you'll meet it The SEC's company\_tickers.json file pairs each ticker and CIK with a company name in a title field, such as NVIDIA CORP and Apple Inc.[[6]](https://www.sec.gov/files/company_tickers.json) In the SEC's company\_tickers.json, some company names are written in capitals, such as MICROSOFT CORP, while others are in mixed case, such as Meta Platforms, Inc.[[6]](https://www.sec.gov/files/company_tickers.json) ## Sources 1. [finetype/labels/definitions\_representation.yaml at main · meridian-online/finetype](https://github.com/meridian-online/finetype/blob/main/labels/definitions_representation.yaml) — FineType 2. [Named-entity recognition - Wikipedia](https://en.wikipedia.org/wiki/Named-entity_recognition) — secondary source 3. [legalName - Schema.org Property](https://schema.org/legalName) — standard 4. [Level 1 Data: LEI-CDF Format 3.1 - LEI Data: Access \& Use - LEI Data – GLEIF](https://www.gleif.org/en/about-lei/common-data-file-format/current-versions/level-1-data-lei-cdf-3-1-format) — documentation 5. [ISO 20275: Entity Legal Forms Code List - Code Lists - LEI Data – GLEIF](https://www.gleif.org/en/lei-data/code-lists/iso-20275-entity-legal-forms-code-list) — documentation 6. [company\_tickers.json](https://www.sec.gov/files/company_tickers.json) — dataset