Entity LEIs (GLEIF)

Verified Legal Entity Identifier (LEI) records for the corridor / RSEI facility parent companies on a site’s watchlist, resolved against the GLEIF registry — the global “who is who / who owns whom” directory. Regenerate with watermark lei.

The watchlist is pinned per corridor, not derived: an entity is on it because a site’s record put it there. One watchlist is committed today — Lima’s — so a site with no LEI records of its own reads this file for the method and holds nothing under it yet.

Source


Dataset	GLEIF LEI — AWS Open Data `s3://gleif` (golden copy)
Access	GLEIF REST API `https://api.gleif.org/api/v1`
License	Creative Commons CC0
Registry	https://registry.opendata.aws/lei/
Docs	https://www.gleif.org/en/lei-data/gleif-golden-copy

The S3 bucket is the bulk golden copy (millions of records, refreshed ~3×/day). For a small watchlist we use the REST API; raw responses cache under the git-ignored data/cache/gleif/, and only the curated YAML here is committed.

Method (litigation discipline)

Every LEI is pinned and fetched by exact 20-character ID — never a fuzzy name match — so the committed record can’t drift onto the wrong legal entity. This is the whole point: a multinational’s US operating subsidiary and its foreign parent routinely share a trading name, and a fuzzy search returns the parent first. Pinning by ID makes which one was meant a reviewable decision instead of a search result.
Entities whose correct legal entity stays ambiguous are kept as unresolved leads, not pinned records (the leads: list — empty when all resolve). Prefer omission over a wrong match.
A direct/ultimate parent that returns 404 means GLEIF holds no reported relationship record — recorded as absent, which is not a claim that no parent exists (it may be an unreported reporting exception). GLEIF relationships are self-reported.

Files

lei-records.yaml — meta provenance + one record per pinned entity (LEI, legal name, jurisdiction, entity/registration status, legal address, reported direct/ultimate parent) + the unresolved leads.

Per-site instances

Which entities a corridor pins, and what the registry said about them, belong to the site whose record named them. They live beside this file under instances/:

Lima’s corridor watchlist

Cataloged datasets — generated from data/catalog/reference/; run watermark catalog render --apply after editing an entry.

`gleif` — Corridor Entity LEIs (GLEIF)

Source: GLEIF — REST API api.gleif.org (Golden Copy) · License: CC0 1.0 · Access: public · Site scope: basin-shared · Refresh: on-demand

Regenerate: watermark gleif

file	type	lfs
`reference/gleif/lei-records.yaml`	application/x-yaml	no

The corridor LEI watchlist at Lima — Allen County, OH

Lima’s pinned watchlist, resolved against GLEIF by the method the dataset README describes. The entities are here because the Allen County, OH record named them — the RSEI facility parents and the corridor’s defense anchor — not because a search surfaced them.

What the registry confirmed

General Dynamics Land Systems Inc. (875500ULXB4CYQSJVA03) reports its ultimate parent as General Dynamics Corporation (9C1X8XOOTYY2FNYTVH06) — an independent registry confirming the GDLS↔GD ownership behind the JSMC operator (the RSEI #4 Allen County facility by Score, and the defense-contractor scan).
Cenovus Energy Inc. (254900LJGL2N2XEMD470) is the post-2021 successor to Husky Energy, the RSEI Lima Refining Co parent.
INEOS USA LLC is pinned to the Delaware entity (549300TWZ86K81VO8O17) by exact legal-name match — deliberately distinct from the Belgian INEOS parent a fuzzy search surfaces first. This is the pin-by-ID rule doing the work it exists for.
The remaining watchlist entities are RSEI Allen County facility parents (Marathon, Ford, Dana, Textron, P&G, Shell); the RSEI instance cross-links the two datasets.

A reported parent that returns 404 is recorded as absent, which is not a claim that no parent exists — see the README’s method section. Nothing on this list is a fuzzy match.