Triple
T31090656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Maybach GLS 600 |
E792375
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz GLS-Class derivative |
C32908
|
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: Mercedes-Benz GLS-Class derivative Context triple: [Mercedes-Maybach GLS 600, instanceOf, Mercedes-Benz GLS-Class derivative]
-
A.
Mercedes-Benz G-Class variant
A Mercedes-Benz G-Class variant is a specific model configuration of the G-Class SUV distinguished by its powertrain, performance tuning, equipment level, and design features while retaining the core G-Class platform and body style.
-
B.
Mercedes-Benz S-Class variant
A Mercedes-Benz S-Class variant is a specific model configuration within the S-Class luxury sedan lineup, distinguished by its unique combination of engine, features, styling, and technology options.
-
C.
Mercedes-Benz E-Class variant
A Mercedes-Benz E-Class variant is a specific model configuration within the E-Class lineup that combines a particular body style, powertrain, and feature set to target a defined performance, luxury, or practicality niche.
-
D.
Mercedes-Maybach vehicle
chosen
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.
-
E.
Mercedes-Benz CLS-Class
The Mercedes-Benz CLS-Class is a luxury four-door coupé that blends elegant, coupe-like styling with the comfort, technology, and performance of a premium sedan.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.