Triple
T3740105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Lambda platform |
E79677
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unibody vehicle architecture |
C10283
|
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: unibody vehicle architecture Context triple: [GM Lambda platform, instanceOf, unibody vehicle architecture]
-
A.
rear-wheel-drive vehicle architecture
A rear-wheel-drive vehicle architecture is a drivetrain layout in which the engine’s power is transmitted primarily to the rear wheels, typically via a driveshaft and rear differential, to provide propulsion and handling characteristics.
-
B.
mid-engine car
A mid-engine car is a vehicle whose engine is located between the front and rear axles, typically behind the passenger compartment, to optimize weight distribution and handling performance.
-
C.
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.
-
D.
sport utility vehicle
A sport utility vehicle is a versatile passenger vehicle that combines elements of on-road cars and off-road trucks, typically offering higher ground clearance, spacious interiors, and optional all-wheel or four-wheel drive for varied driving conditions.
-
E.
automotive platform
chosen
An automotive platform is a shared, standardized set of structural, mechanical, and electronic components that underpins multiple vehicle models to streamline development, reduce costs, and enable design flexibility.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:34 p.m.