Triple
T35330037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Racing Development |
E1020292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subsidiary of Toyota Motor Corporation |
C6409
|
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 of Toyota Motor Corporation Context triple: [Toyota Racing Development, instanceOf, subsidiary of Toyota Motor Corporation]
-
A.
Toyota subsidiary
chosen
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.