Triple
T35751377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Body Control suspension |
E1033329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hydropneumatic 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: hydropneumatic suspension system Context triple: [Active Body Control suspension, instanceOf, hydropneumatic suspension system]
-
A.
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.
-
B.
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.
-
C.
modular load-carrying system
A modular load-carrying system is a configurable assembly of interchangeable components designed to transport, support, and adapt to varying types and amounts of loads in different operational contexts.
-
D.
vehicle dynamics system
A vehicle dynamics system is a conceptual class that models and controls how a vehicle responds to driver inputs and external forces through its motion, stability, and handling behavior.
-
E.
rear‑wheel steering system
A rear-wheel steering system is a vehicle mechanism that actively turns the rear wheels, in coordination or opposition to the front wheels, to improve maneuverability, stability, and handling.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.