Triple
T35751298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz 280 SL |
E1033327
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz SL-Class variant |
C32783
|
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 SL-Class variant Context triple: [Mercedes-Benz 280 SL, instanceOf, Mercedes-Benz SL-Class variant]
-
A.
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.
-
B.
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.
-
C.
Mercedes-Benz SL-Class
The Mercedes-Benz SL-Class is a luxury grand-touring roadster that combines high-performance engineering with premium comfort, advanced technology, and iconic open-top styling.
-
D.
Mercedes-Benz SL generation
A Mercedes-Benz SL generation is a distinct iteration of the SL grand-touring roadster series, defined by its specific design language, engineering platform, technology features, and production years within the model’s long-running lineage.
-
E.
Mercedes-Benz SL-Class generation
chosen
A Mercedes-Benz SL-Class generation is a distinct production era of the SL grand-touring roadster, defined by a specific platform, design language, engineering features, and technological updates that differentiate it from other SL iterations.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.