Triple
T21034105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaha Motor USA |
E518142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yamaha Motor Company subsidiary |
C44514
|
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: Yamaha Motor Company subsidiary Context triple: [Yamaha Motor USA, instanceOf, Yamaha Motor Company subsidiary]
-
A.
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.
-
B.
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.
-
C.
Sony Group subsidiary
A Sony Group subsidiary is a company that is majority-owned or otherwise controlled by Sony Group Corporation, operating under its corporate umbrella while focusing on specific business areas such as electronics, entertainment, or financial services.
-
D.
Fujitsu subsidiary
A Fujitsu subsidiary is a company that is owned or controlled by Fujitsu Limited and operates as part of its broader corporate group, often focusing on specific markets, technologies, or services.
-
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. 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2 p.m.