Triple
T27996986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Sports Car Architecture (bonded aluminium chassis) |
E707039
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicle chassis technology |
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: vehicle chassis technology Context triple: [Lotus Sports Car Architecture (bonded aluminium chassis), instanceOf, vehicle chassis technology]
-
A.
drivetrain technology
Drivetrain technology encompasses the systems and components that transmit power from a vehicle’s engine or motor to its wheels, optimizing efficiency, performance, and control.
-
B.
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.
-
C.
automotive suspension system
An automotive suspension system is the integrated assembly of springs, dampers, linkages, and related components that connects a vehicle’s body to its wheels to control ride comfort, handling, and road shock isolation.
-
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.
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.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:54 p.m.