Triple
T38355793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar XJR |
E1046323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jaguar XJ variant |
C63455
|
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 XJ variant Context triple: [Jaguar XJR, instanceOf, Jaguar XJ variant]
-
A.
Jaguar E-Type variant
A Jaguar E-Type variant is a specific model configuration or evolution of the classic Jaguar E-Type sports car, distinguished by unique combinations of body style, engine, production period, and performance or design features.
-
B.
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.
-
C.
Bentley vehicle
A Bentley vehicle is a high-end luxury automobile that combines handcrafted craftsmanship, advanced engineering, and powerful performance to deliver an exceptionally refined driving experience.
-
D.
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.
-
E.
Maserati Levante variant
A Maserati Levante variant is a specific configuration of the Levante SUV distinguished by unique combinations of engine performance, trim level, design features, and equipment packages.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.