Triple
T18816699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiat Uno (Type 146) |
E460154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fiat Uno model generation |
C33193
|
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: Fiat Uno model generation Context triple: [Fiat Uno (Type 146), instanceOf, Fiat Uno model generation]
-
A.
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.
-
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.
automobile model
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.
-
D.
automobile model variant
chosen
An automobile model variant is a specific version of a car model distinguished by particular features, options, performance characteristics, or styling differences within the same overall model line.
-
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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 11:55 a.m.