Triple
T28807971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyactiv-Body platform (third generation) |
E727431
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mazda vehicle architecture |
C45046
|
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: Mazda vehicle architecture Context triple: [Skyactiv-Body platform (third generation), instanceOf, Mazda 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.
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.
-
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.
shared vehicle architecture
chosen
A shared vehicle architecture is a common, modular platform designed to support multiple vehicle models or types, enabling reuse of components, streamlined engineering, and reduced development costs.
-
E.
automotive all-wheel-drive system
An automotive all-wheel-drive system is a drivetrain configuration that automatically distributes engine power to all four wheels to enhance traction, stability, and handling across varying road and weather conditions.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:29 a.m.