Triple
T11330447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Highlander (XU70) |
E268328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Toyota Highlander generation |
C29571
|
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 Highlander generation Context triple: [Toyota Highlander (XU70), instanceOf, Toyota Highlander generation]
-
A.
Holden Commodore generation
A Holden Commodore generation is a distinct design and engineering iteration of the Holden Commodore model line, characterized by a specific platform, styling, technology set, and production timeframe.
-
B.
Holden Torana generation
The Holden Torana generation class represents a specific iteration of the Holden Torana model distinguished by its production years, design features, mechanical specifications, and market positioning within the vehicle’s historical lineage.
-
C.
Chevrolet Trailblazer variant
A Chevrolet Trailblazer variant is a specific model configuration within the Trailblazer lineup, distinguished by unique combinations of features, trim levels, performance options, and styling elements.
-
D.
Opel Corsa generation
An Opel Corsa generation represents a distinct production era of the Opel Corsa model characterized by specific design, engineering, technology, and feature updates that differentiate it from previous and subsequent versions.
-
E.
Opel Vectra generation
An Opel Vectra generation represents a distinct production era of the Opel Vectra model, characterized by specific design, engineering, and technological features that differentiate it from other iterations.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:32 p.m.