# Legal Entity Relationships (GLEIF Level 2)

> Dated relations between legal entities by LEI: direct and ultimate parents, fund managers, umbrellas, feeders and branches, as asserted, revised and ended.

InfoTrie's legal entity relationship dataset is a graph of dated, sourced relations between legal entities named by a strong identifier (lei:, cik:): who is consolidated by whom, directly and ultimately, which management company manages a fund, which sub-fund belongs to which umbrella, feeders and their master funds, branches, and a fund's share classes by ISIN. It is rebuilt from GLEIF's Level 2 relationship records every day, and it is bitemporal: each relation says when it held and when InfoTrie knew it, so the graph can be read as it stood on any past day.

Status: In rollout — available on request.

## Key facts

| | |
|---|---|
| Relations | Direct and ultimate parent, fund manager, sub-fund of an umbrella, feeder, branch; share classes (ISIN) to their fund; 13F filer families |
| Nodes | Legal entities of every kind by LEI (companies, funds, umbrellas, management companies, groups), SEC filers by CIK, securities by ISIN |
| Point in time | Bitemporal: valid from / to, and known from / to |
| Measured run | 489,183 relations from GLEIF's file of 3 November 2026 |
| Update frequency | Daily; a day's file that would drop more than 10 % of the open relations is refused and logged |
| Traversal | 1 or 2 hops, up or down the structure, as of a past day |
| Delivery | REST API and MCP tool (rollout), InfoTrie console datasets; Enterprise and Bespoke plans |

## Sources

- GLEIF Level 2 relationship records
- GLEIF ISIN-to-LEI mapping
- SEC Form 13F filer relations

## Data dictionary

| Field | Type | Description |
|---|---|---|
| `subject` | string | The entity the relation is about, e.g. lei:<child> |
| `relation` | string | The relation, e.g. IS_DIRECTLY_CONSOLIDATED_BY, IS_ULTIMATELY_CONSOLIDATED_BY, IS_FUND_MANAGED_BY, IS_SUBFUND_OF, IS_ISSUED_BY |
| `object` | string | The other entity, e.g. lei:<parent> |
| `valid_from / valid_to` | timestamp | When the relation held |
| `known_from / known_to` | timestamp | When InfoTrie knew it |
| `source_label` | string | The source's public label |
| `evidence_ref` | string | The record or file the relation was read from |

## Use cases

- **Group structures.** Map a group from its ultimate parent down to its subsidiaries and branches.
- **Fund ranges.** List the funds a management company manages, their umbrellas and their share classes.
- **Counterparty and issuer risk.** Roll exposures up to the ultimate parent, as the structure stood on any past day.

## Delivery

- REST API (rollout): relations of an entity, by direction, relation type, depth (1 or 2 hops) and as-of day, JSON, with an API key
- MCP tool (rollout): entity_neighbors, read-only
- InfoTrie console: the dataset's daily snapshots and quality status
- On the Enterprise and Bespoke plans

## FAQ

### Can I see the structure as it was in the past?

Yes. Every relation carries when it held and when InfoTrie knew it; ask for the graph as of a day and you get what was known then.

### Does it cover funds and asset managers, not only companies?

Yes. Nodes are legal entities of every kind: funds, sub-funds, umbrellas, management companies and their groups, as well as companies. A fund's role is read from its relations.

### How do I credit the source?

Name GLEIF (the Global Legal Entity Identifier Foundation) as the source of the Level 2 relationship records and the ISIN-to-LEI mapping; each relation carries its source's label.

## See also

- [Legal Entities (GLEIF Level 1)](https://infotrie.com/datasets/legal-entities-lei)
- [Fund Holdings (SEC N-PORT)](https://infotrie.com/datasets/fund-holdings-n-port)
- [Form 13F Institutional Holdings](https://infotrie.com/datasets/13f-institutional-holdings)
- [Bond Reference Data (Terms)](https://infotrie.com/datasets/bond-reference-data)
- [API reference (entities)](https://infotrie.com/docs/api-reference)
- [Request a sample or a quote](https://infotrie.com/contact)