Triple
T29982496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weissach axle independent suspension |
E761632
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rear suspension system |
C8155
|
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: rear suspension system Context triple: [Weissach axle independent suspension, instanceOf, rear suspension system]
-
A.
automotive suspension system
chosen
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.
-
B.
adaptive suspension system
An adaptive suspension system is a vehicle suspension technology that continuously adjusts damping and stiffness in real time based on driving conditions, road surface, and driver inputs to optimize comfort, handling, and stability.
-
C.
rear-engined car
A rear-engined car is a vehicle whose engine is mounted behind the rear axle, typically improving traction but affecting handling dynamics compared to front- or mid-engined layouts.
-
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.
automotive seating system
An automotive seating system is an integrated assembly of seats, structures, mechanisms, and comfort/safety features designed to support, position, and protect vehicle occupants during driving and collisions.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:35 p.m.