Triple
T18138795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM U platform |
E434205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | General Motors vehicle architecture |
C2728
|
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: General Motors vehicle architecture Context triple: [GM U platform, instanceOf, General Motors vehicle architecture]
-
A.
automotive architecture
Automotive architecture is the conceptual and structural design framework that defines how a vehicle’s key systems, components, and spatial layout are organized and integrated to meet performance, safety, and user experience goals.
-
B.
General Motors platform
chosen
A General Motors platform is a shared underlying vehicle architecture, including structural, mechanical, and sometimes electronic components, used across multiple GM models to streamline design, production, and costs.
-
C.
unibody chassis architecture
A unibody chassis architecture is a vehicle construction method where the body and frame are integrated into a single, rigid structural shell that provides both support and crash protection.
-
D.
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.
-
E.
Ford vehicle platform
A Ford vehicle platform is a shared engineering and structural foundation used across multiple Ford models to standardize components, reduce costs, and streamline design and production.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.