Triple
T13521015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz SL 500 |
E322894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz SL-Class model |
C1018
|
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 model Context triple: [Mercedes-Benz SL 500, instanceOf, Mercedes-Benz SL-Class model]
-
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.
Porsche vehicle
A Porsche vehicle is a high-performance, premium automobile engineered for dynamic driving, combining advanced technology, distinctive design, and luxury features under the Porsche brand.
-
C.
automobile model
chosen
An automobile model is a specific version of a vehicle produced by a manufacturer, defined by a distinct combination of design, features, and specifications that differentiates it from other vehicles in the product lineup.
-
D.
Mercedes-Benz division
A Mercedes-Benz division is an organizational unit within the Mercedes-Benz company responsible for a specific product line, market segment, or operational function, such as passenger cars, commercial vehicles, or financial services.
-
E.
Oldsmobile Toronado variant
A specific model or trim level of the Oldsmobile Toronado, distinguished by unique features, styling, performance characteristics, or production details that set it apart from the standard version.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:44 p.m.