Triple
T16740149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyundai Motor Manufacturing Alabama |
E406813
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hyundai Motor Company subsidiary |
C37846
|
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: Hyundai Motor Company subsidiary Context triple: [Hyundai Motor Manufacturing Alabama, instanceOf, Hyundai Motor Company subsidiary]
-
A.
Kia Corporation subsidiary
A Kia Corporation subsidiary is a legally distinct company that is majority-owned or controlled by Kia Corporation to support its automotive manufacturing, distribution, or related business operations.
-
B.
Toyota subsidiary
A Toyota subsidiary is a legally distinct company in which Toyota Motor Corporation holds a controlling interest, operating under its strategic direction while managing specific regional markets, product lines, or business functions.
-
C.
Toyota Group company
A Toyota Group company is any corporation that is directly or indirectly controlled by, affiliated with, or strategically partnered with Toyota Motor Corporation as part of its broader corporate group.
-
D.
Ford Motor Company division
A Ford Motor Company division is an organizational unit within Ford responsible for specific product lines, markets, or business functions, operating under the broader corporate structure and strategy of the company.
-
E.
Airbus subsidiary
An Airbus subsidiary is a legally distinct company that is owned or controlled by Airbus and operates specific aspects of its aerospace, defense, or related business activities.
- F. None of above. chosen
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.