Triple
T28858245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkin Blower |
E728794
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bentley 4½ Litre variant |
C46213
|
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: Bentley 4½ Litre variant Context triple: [Birkin Blower, instanceOf, Bentley 4½ Litre 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.
Bentley vehicle
chosen
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.
-
C.
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.
-
D.
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.
-
E.
Bristol Blenheim variant
A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:46 a.m.