Triple
T4403907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | e-Pedal (second generation) |
E93680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | one-pedal driving system |
C15930
|
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: one-pedal driving system Context triple: [e-Pedal (second generation), instanceOf, one-pedal driving system]
-
A.
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.
-
B.
self-balancing personal transporter
A self-balancing personal transporter is a compact, motorized vehicle that uses gyroscopic sensors and dynamic stabilization to keep itself upright while carrying a single rider.
-
C.
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.
-
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.
micromobility device
A micromobility device is a small, lightweight, typically single-passenger vehicle—often electric-powered—designed for short-distance urban travel, such as e-scooters, e-bikes, and similar compact transport options.
- F. None of above. chosen
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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:28 p.m.