Triple
T36116323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Multi-purpose Vehicle (IMV) project |
E1044623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toyota project |
C63373
|
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: Toyota project Context triple: [International Multi-purpose Vehicle (IMV) project, instanceOf, Toyota project]
-
A.
Toyota vehicle platform
A Toyota vehicle platform is a shared engineering and structural foundation used across multiple Toyota and Lexus models to standardize components, improve manufacturing efficiency, and enhance performance and safety.
-
B.
Toyota brand
Toyota brand represents a globally recognized automotive manufacturer known for reliable, fuel-efficient vehicles, continuous improvement (Kaizen), and strong value for money.
-
C.
Toyota motorsport program
The Toyota motorsport program is the coordinated global effort by Toyota to design, develop, and campaign racing vehicles across multiple disciplines—such as rally, endurance, and single-seater series—to advance technology, strengthen brand image, and support driver and engineering talent.
-
D.
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.
-
E.
Toyota Motor Europe initiative
A Toyota Motor Europe initiative is a strategic program or project undertaken by Toyota’s European division to advance its business, sustainability, innovation, or community objectives within the European market.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.