Triple
T7208998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Cruze (J300) |
E148750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | first generation Chevrolet Cruze |
C1018
|
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: first generation Chevrolet Cruze Context triple: [Chevrolet Cruze (J300), instanceOf, first generation Chevrolet Cruze]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Chevrolet vehicle line
A Chevrolet vehicle line is a collection of related Chevrolet-branded models that share a common platform, design language, and market segment purpose within the manufacturer’s overall product portfolio.
-
E.
automobile model
chosen
An automobile model is a specific version of a vehicle produced by a manufacturer, defined by a distinct combination of design, features, and specifications that differentiates it from other vehicles in the product lineup.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:52 p.m.