Triple
T17930728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM Ecotec LNF |
E448323
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turbocharged gasoline engine |
C8796
|
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: turbocharged gasoline engine Context triple: [GM Ecotec LNF, instanceOf, turbocharged gasoline engine]
-
A.
hyperbar turbocharged diesel engine
A hyperbar turbocharged diesel engine is an internal combustion engine that uses a high-pressure turbocharging system, often with multiple compressor stages, to significantly increase intake air density and boost power, efficiency, and performance over conventional turbocharged diesels.
-
B.
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.
-
C.
gas turbine engine
A gas turbine engine is a continuous-flow internal combustion engine that compresses air, mixes it with fuel, burns the mixture, and expands the hot gases through turbine and nozzle stages to produce mechanical power or thrust.
-
D.
internal combustion engine
chosen
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.
-
E.
turbofan engine
A turbofan engine is a type of air-breathing jet engine that uses a large fan driven by a gas turbine to produce thrust through both accelerated bypass air and exhaust gases for efficient high-speed propulsion.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:20 a.m.