Triple
T30435234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Fuel Management |
E774291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fuel-saving engine technology |
C56497
|
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: fuel-saving engine technology Context triple: [Active Fuel Management, instanceOf, fuel-saving engine technology]
-
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.
internal combustion engine
An internal combustion engine is a machine that converts the chemical energy of fuel into mechanical work by burning the fuel-air mixture within its cylinders to produce controlled explosions that drive pistons or rotors.
-
C.
multi-fuel engine
A multi-fuel engine is a power unit designed to operate efficiently on more than one type of fuel, such as gasoline, diesel, ethanol, or alternative fuels, without requiring major mechanical modifications.
-
D.
gas turbine–powered car
A gas turbine–powered car is a road vehicle that uses a gas turbine engine, rather than a conventional piston engine, to convert fuel into mechanical power for propulsion.
-
E.
internal combustion engine vehicle
An internal combustion engine vehicle is a motorized transport device that converts the chemical energy of fuel into mechanical work through controlled combustion within an engine to drive its wheels or propulsion system.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:07 p.m.