Triple
T36075908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series 1.5 Jaguar E-Type |
E1043494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jaguar E-Type variant |
C62504
|
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: Jaguar E-Type variant Context triple: [Series 1.5 Jaguar E-Type, instanceOf, Jaguar E-Type variant]
-
A.
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.
-
B.
Lancia Aurelia variant
A Lancia Aurelia variant is a specific model or configuration within the Aurelia series that differs in features such as body style, engine specification, or production year while retaining the core design and engineering characteristics of the original Lancia Aurelia.
-
C.
Lamborghini Countach variant
A Lamborghini Countach variant is a specific model iteration of the iconic mid‑engine Italian supercar distinguished by unique styling, performance tuning, and limited-production features.
-
D.
Lotus Esprit model
The Lotus Esprit model is a mid-engine sports car renowned for its sharp wedge-shaped design, lightweight construction, and agile performance, produced by British manufacturer Lotus from the 1970s through the early 2000s.
-
E.
Lotus road car
A Lotus road car is a lightweight, high-performance sports car designed for exceptional handling and driver engagement, derived from the brand’s racing heritage but engineered for everyday road use.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.