Triple
T30435233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Fuel Management |
E774291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cylinder deactivation technology |
C56496
|
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: cylinder deactivation technology Context triple: [Active Fuel Management, instanceOf, cylinder deactivation technology]
-
A.
dual overhead camshaft engine
A dual overhead camshaft engine is an internal combustion engine design that uses two camshafts per cylinder bank, mounted above the cylinders, to independently operate intake and exhaust valves for improved performance and efficiency.
-
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.
Ecotec engine
An Ecotec engine is a family of fuel-efficient, low-emission internal combustion engines developed by General Motors, designed to deliver reliable performance across a range of compact and midsize vehicles.
-
D.
W-configuration engine
A W-configuration engine is an internal combustion engine with four cylinder banks arranged in a "W" shape around the crankshaft, effectively combining two narrow-angle V engines to create a compact, high-output powerplant.
-
E.
H-24 engine
An H-24 engine is a 24-cylinder internal combustion engine arranged in an "H" configuration, effectively combining two horizontally opposed 12-cylinder engines to drive a common output shaft.
- 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.