Triple
T30142617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turbocharged Direct Injection |
E766168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal combustion engine technology |
C54967
|
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: internal combustion engine technology Context triple: [Turbocharged Direct Injection, instanceOf, internal combustion engine technology]
-
A.
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.
-
B.
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.
-
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.
automotive fuel injection system
chosen
An automotive fuel injection system is a mechanism that precisely meters and delivers fuel into an engine’s combustion chambers (or intake ports) under electronic control to optimize performance, efficiency, and emissions.
-
E.
heat engine
A heat engine is a system that converts thermal energy into mechanical work by exploiting a temperature difference between a hot reservoir and a cold reservoir.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:18 p.m.