Entity Name
representation.text.entity_nameNon-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.
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] 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]
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]
Use
Schema.org defines legalName as the official name of an organisation, for example the registered company name.[3] GLEIF's LEI-CDF 3.1 format records the legal name of each entity in a LegalName element.[4] 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] 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] LEI-CDF 3.1 keeps ASCII-transliterated (Latin or Romanised) names in a separate TransliteratedOtherEntityNames element.[4] 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] GLEIF's ELF Code List, in its February 2026 version, lists more than 3,600 entity legal forms across more than 200 jurisdictions.[5] 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] GLEIF's ELF page warns that a Dutch BV is not a German GmbH and is not a private limited liability company.[5] 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] 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]
Sources
- [1]finetype/labels/definitions_representation.yaml at main · meridian-online/finetypeFineType
- [2]Named-entity recognition - Wikipediasecondary source
- [3]legalName - Schema.org Propertystandard
- [4]Level 1 Data: LEI-CDF Format 3.1 - LEI Data: Access & Use - LEI Data – GLEIFdocumentation
- [5]ISO 20275: Entity Legal Forms Code List - Code Lists - LEI Data – GLEIFdocumentation
- [6]company_tickers.jsondataset
Detection notes
Addresses full_name overcall: 3,086 SOTAB columns misclassified as person names are actually entity names (songs, restaurants, products, venues). CharCNN can learn to distinguish entity_name from full_name via business suffixes, numbers, and mixed-case patterns. broad_words designation means column-level disambiguation can override with header hints.
In Meridian's open data
- gleif
legal_name - edgar
company_name - edgar_gleif
company_name - edgar_gleif
legal_nameconfidence 0.56
Use it
$ finetype infer -i "The Olive Garden" --mode column
→ representation.text.entity_name
SELECT ft_infer('The Olive Garden');
-- → 'representation.text.entity_name'CAST({col} AS VARCHAR)Schema
https://meridian.online/schemas/representation.text.entity_name · Frictionless type string
finetype taxonomy representation.text.entity_name -o json-schema