Triple
T3707107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz EQE |
E80919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric executive car |
C12044
|
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: electric executive car Context triple: [Mercedes-Benz EQE, instanceOf, electric executive car]
-
A.
electric luxury sedan
chosen
An electric luxury sedan is a high-end, four-door passenger car powered solely by electric motors and batteries, offering premium comfort, advanced technology, and refined performance.
-
B.
electric vehicle platform
An electric vehicle platform is a modular, shared chassis architecture that integrates the battery pack, electric motors, suspension, and core electronics to serve as the foundation for multiple EV models.
-
C.
electric semi-truck
An electric semi-truck is a heavy-duty commercial vehicle powered solely by electric batteries and motors, designed to haul large freight loads with reduced emissions and operating costs compared to diesel trucks.
-
D.
battery electric vehicle architecture
Battery electric vehicle architecture is the integrated system design that defines how the battery pack, electric drivetrain, power electronics, control systems, and supporting components are configured and interact to deliver propulsion, safety, efficiency, and functionality in an all-electric vehicle.
-
E.
mid-size executive car
A mid-size executive car is a premium, comfortably appointed sedan or estate offering higher levels of refinement, performance, and features than mainstream family cars, aimed at professional and business users.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.