Triple
T32710748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford of Canada |
E836397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ford Motor Company subsidiary |
C37942
|
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: Ford Motor Company subsidiary Context triple: [Ford of Canada, instanceOf, Ford Motor Company subsidiary]
-
A.
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.
-
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.
Hyundai Motor Company subsidiary
A Hyundai Motor Company subsidiary is a legally distinct company that is majority-owned or controlled by Hyundai Motor Company and operates under its strategic and financial oversight within the broader Hyundai corporate group.
-
D.
automotive company subsidiary
chosen
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.
-
E.
Hyundai subsidiary
A Hyundai subsidiary is a company that is owned or controlled by the Hyundai Motor Group or Hyundai Corporation to conduct specific business operations under the broader Hyundai brand.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:10 a.m.