Triple
T33429200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers L 55 |
E856077
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liquid-cooled inline engine |
C2761
|
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: liquid-cooled inline engine Context triple: [Junkers L 55, instanceOf, liquid-cooled inline engine]
-
A.
liquid-cooled aircraft engine
A liquid-cooled aircraft engine is a piston or reciprocating powerplant that uses a circulating liquid coolant, typically water or glycol, to absorb and dissipate heat from the engine cylinders and heads, enabling efficient temperature control and reliable operation in flight.
-
B.
liquid-cooled aero engine
chosen
A liquid-cooled aero engine is an aircraft powerplant that uses a circulating liquid coolant, typically water or glycol, to absorb and dissipate heat from the engine, enabling higher performance and more consistent operating temperatures than air-cooled designs.
-
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.
V12 engine
A V12 engine is a twelve-cylinder internal combustion engine with two banks of six cylinders arranged in a V configuration around a common crankshaft, providing smooth, high-power performance.
-
E.
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.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.