Triple
T30142285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audi Space Frame |
E766160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | lightweight vehicle architecture |
C33156
|
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: lightweight vehicle architecture Context triple: [Audi Space Frame, instanceOf, lightweight 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.
light utility vehicle
A light utility vehicle is a small, versatile motor vehicle designed to transport people, light cargo, or equipment, often with off-road or multi-terrain capability.
-
C.
light commercial vehicle platform
A light commercial vehicle platform is a modular structural and mechanical base designed to support various small cargo and utility vehicle configurations while optimizing payload, durability, and cost.
-
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.
automotive architecture
chosen
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.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:18 p.m.