# Ownership Investigator Scrutica # Entities Cite Facilities, companies, and countries — the who and where of compute — each with its full filter, sort, export, and provenance toolkit, plus the Investigator to resolve any identifier into its documented ownership chain. The map plots the same universe in space. Search ## Investigator Feed the Investigator a compute entity in whatever shape you have it — operator name, facility id, ticker, CIK, LEI, a BIS-designated entity, a sovereign LP, or an alias — and the walker climbs the documented chain hop by hop, citing data\_source, source\_url, as-of date, and confidence inline on each edge rather than collecting them in a footnote. Conflicting parents both appear; a chain that terminates in opacity says so, with the public-record gap labelled as a gap, not as proof there is no further parent. Backbone provenance ## 58,021 ownership edges, each one open to the SEC filing it came from Of the 95,045 parent-subsidiary relationships in this graph, 58,021 — 61% — were lifted directly from SEC EDGAR (Exhibit 21 subsidiary lists and the filings around them), and every one carries the sec.gov URL of the document it was read from. Click any of those hops and you land on the primary source, not a citation of a citation. The rest of the graph fills in private companies and foreign parents the SEC never sees; those edges are flagged as such and never dressed up as something they aren’t. Investigate an entity Entity to investigateInvestigate Accepts: organization name (Equinix), ticker (NVDA), CIK (1045810), LEI (20-char), licensed-database company id (12817-90), BIS-designated entity, sovereign LP (“Mubadala Investment Company”), organization alias, or canonical Scrutica id (org-\*). Fuzzy substring fallback runs only when nothing else matches, and lands with low confidence stamped on it. Start with a known entity - [ NVIDIA Corporation Public company · ticker NVDA ](/companies/org-nvidia#ownership) - [ Equinix, Inc. Public colocation REIT · ticker EQIX ](/companies/org-equinix#ownership) - [ TSMC Taiwanese foundry · deep supply-chain ancestry ](/companies/org-tsmc#ownership) - [ Huawei Technologies BIS-designated entity · affiliate closure ](/companies/org-huawei#ownership) - [ ASML Dutch lithography · Euronext ASML ](/companies/org-asml#ownership) - [ Anthropic Private AI lab ](/companies/org-anthropic#ownership) Investigator · Regulatory reach ## Investigator vs. Impact Pre-Scorer The Investigator is _entity-centric_ — you give it an entity, it climbs that entity’s ancestors. The [Impact Pre-Scorer](/export-controls/impact) is _rule-centric_ — you give it a hypothetical BIS Entity List designation and it returns every facility the cascaded designation reaches. Same ownership substrate, opposite query directions; the Investigator is what an analyst opens to build a case, the Pre-Scorer is what a policy evaluator opens to score one. Each hop on an entity page carries data\_source, source\_url (where one exists), as-of date, and confidence right on the line — no footnotes to chase. Affiliate closures of BIS / OFAC / equivalent designations sit in the right rail; so do sovereign LP commitments routed through a fund. The page is text-first on purpose; researchers paste sentences into their citation managers, not screenshots. Related analysis [ Supply ChainControls & Supply The corporate edges this investigator walks to ultimate beneficial owner](/supply-chain)[ Export ControlsControls & Supply Entity-level designations applied at each UBO node along the chain](/export-controls)[ Chokepoint Activity Feed Live ownership-change activity in the same graph this investigator traverses](/supply-chain/concentration#activity)[ Sovereign AICompute & Capability Sovereign-fund LP chains terminating in portfolio-company UBOs](/sovereign-ai) Notify me about New dataMajor featuresRegulatoryResearch Email addressSubscribe [CC BY-SA 4.0·© 2026 Scrutica](https://creativecommons.org/licenses/by-sa/4.0/ "Creative Commons Attribution-ShareAlike 4.0") Built for the AI governance research community