Triple
T29153642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bentayga Mulliner |
E738978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bentley Bentayga 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 Bentayga variant Context triple: [Bentayga Mulliner, instanceOf, Bentley Bentayga 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.
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.
-
C.
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.
-
D.
Maserati Grecale variant
A Maserati Grecale variant is a specific configuration of the Grecale SUV distinguished by its unique combination of powertrain, performance tuning, design features, and equipment level within the model lineup.
-
E.
Mercedes-Maybach vehicle
A Mercedes-Maybach vehicle is an ultra-luxury automobile that combines advanced Mercedes-Benz engineering with elevated comfort, bespoke craftsmanship, and exclusive design features for a premium driving and chauffeured experience.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:43 a.m.