Triple
T35751421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sensotronic Brake Control |
E1033330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electro-hydraulic brake-by-wire system |
C57227
|
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: electro-hydraulic brake-by-wire system Context triple: [Sensotronic Brake Control, instanceOf, electro-hydraulic brake-by-wire system]
-
A.
one-pedal driving system
A one-pedal driving system is a vehicle control feature that allows the driver to accelerate and decelerate using only the accelerator pedal by automatically applying regenerative and/or friction braking when the pedal is released.
-
B.
vehicle electronic control system
chosen
A vehicle electronic control system is an integrated hardware and software platform that monitors sensor inputs and manages actuators to optimize and coordinate a vehicle’s performance, safety, and efficiency.
-
C.
hybrid powertrain technology
Hybrid powertrain technology integrates an internal combustion engine with one or more electric motors and a battery system to optimize fuel efficiency, reduce emissions, and enhance vehicle performance through intelligent power management.
-
D.
gasoline-electric hybrid system
A gasoline-electric hybrid system is a powertrain that combines an internal combustion engine with one or more electric motors and a battery to improve fuel efficiency, reduce emissions, and optimize vehicle performance.
-
E.
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.
- 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.