Triple
T35757978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosch mechanical fuel injection |
E1033497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mechanical fuel injection system |
C62269
|
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: mechanical fuel injection system Context triple: [Bosch mechanical fuel injection, instanceOf, mechanical fuel injection system]
-
A.
automotive fuel injection system
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.
-
B.
electronic fuel injection system
An electronic fuel injection system is a computer-controlled mechanism that precisely meters and delivers fuel into an engine’s cylinders based on real-time sensor data to optimize performance, efficiency, and emissions.
-
C.
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.
-
D.
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.
-
E.
H‑type engine
An H-type engine is an internal combustion engine configuration featuring two horizontally opposed engines stacked vertically and connected to a common crankshaft system, forming an "H" shape to provide compact, high-power output.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.