Triple
T1109972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PV-12 |
E25571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liquid-cooled 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 engine Context triple: [PV-12, instanceOf, liquid-cooled 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.
water-cooled reactor
A water-cooled reactor is a nuclear reactor that uses water as both a coolant to remove heat from the reactor core and often as a moderator to slow down neutrons, enabling a controlled fission chain reaction.
-
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.
liquid-fueled rocket engine
A liquid-fueled rocket engine is a propulsion system that burns liquid propellants—typically a fuel and an oxidizer—pumped into a combustion chamber to produce high-velocity exhaust for thrust.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:43 p.m.