Triple
T3927400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Kinsei |
E93308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air‑cooled engine |
C1941
|
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: air‑cooled engine Context triple: [Mitsubishi Kinsei, instanceOf, air‑cooled engine]
-
A.
liquid-cooled aero engine
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.
-
B.
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.
-
C.
aircraft piston engine
chosen
An aircraft piston engine is a reciprocating internal combustion engine that converts the linear motion of pistons into rotational power to drive a propeller and provide thrust for an aircraft.
-
D.
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.
-
E.
V6 engine
A V6 engine is an internal combustion engine with six cylinders arranged in two banks of three forming a "V" shape around a common crankshaft, balancing performance, compactness, and efficiency.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:23 p.m.