Triple
T31336853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-twin |
E799197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal combustion engine layout |
C61134
|
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 layout Context triple: [L-twin, instanceOf, internal combustion engine layout]
-
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.
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.
-
C.
inline-six engine
An inline-six engine is a type of internal combustion engine with six cylinders arranged in a single straight line along the crankcase, known for its smooth operation and balanced performance.
-
D.
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.
-
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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:16 p.m.