Triple
T13069807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G22 |
E329426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | BMW 4 Series generation |
C12397
|
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: BMW 4 Series generation Context triple: [G22, instanceOf, BMW 4 Series generation]
-
A.
BMW vehicle line
chosen
A BMW vehicle line is a distinct series of BMW-branded automobiles that share a common platform, design language, and performance characteristics, targeting a specific market segment or customer need.
-
B.
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.
-
C.
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.
-
D.
Bentley Continental GT variant
A Bentley Continental GT variant is a specific model configuration within the Continental GT lineup that combines a distinct powertrain, chassis tuning, and bespoke design features to deliver a tailored blend of performance, luxury, and style.
-
E.
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.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9 p.m.