Triple
T30122682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNC NE |
E765600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subsidiary or division of a multinational corporation |
C13398
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: subsidiary or division of a multinational corporation Context triple: [MNC NE, instanceOf, subsidiary or division of a multinational corporation]
-
A.
subordinate organization
A subordinate organization is an entity that operates under the authority, control, or oversight of a higher-level organization, carrying out specific functions or responsibilities delegated to it.
-
B.
Berkshire Hathaway subsidiary
A Berkshire Hathaway subsidiary is a company in which Berkshire Hathaway holds a controlling ownership stake, operating independently while contributing to the conglomerate’s overall financial performance and strategic objectives.
-
C.
subsidiary business
chosen
A subsidiary business is a company that is controlled by another, typically larger, parent company through ownership of a majority of its voting shares.
-
D.
subsidiary structure
A subsidiary structure is an organizational entity that is legally separate but controlled by a parent company, created to manage specific operations, risks, or markets under the broader corporate umbrella.
-
E.
automotive company subsidiary
An automotive company subsidiary is a legally distinct company controlled by a larger parent automaker that focuses on specific functions such as manufacturing, design, regional operations, or specialized vehicle brands within the overall corporate structure.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:13 p.m.