Triple
T36074801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H247 |
E1043469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mercedes-Benz internal model code |
C32804
|
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 internal model code Context triple: [H247, instanceOf, Mercedes-Benz internal model code]
-
A.
BMW internal model code
A BMW internal model code is a manufacturer-assigned alphanumeric identifier used within BMW to uniquely designate a specific vehicle platform, generation, or variant for engineering, production, and cataloging purposes.
-
B.
Mercedes-Benz chassis code
chosen
A Mercedes-Benz chassis code is an alphanumeric designation used by the manufacturer to identify the specific platform, body style, and generation of a Mercedes-Benz vehicle.
-
C.
Lexus internal chassis code
A Lexus internal chassis code is a manufacturer-assigned alphanumeric identifier that designates a specific Lexus vehicle platform, generation, and major mechanical configuration for engineering and cataloging purposes.
-
D.
Nissan internal chassis code
A Nissan internal chassis code is a manufacturer-assigned alphanumeric identifier used to distinguish specific vehicle platforms, generations, and configurations within Nissan’s product lineup.
-
E.
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.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.