Triple
T545684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurojet EJ200 |
E12727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aircraft engine |
C4285
|
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: military aircraft engine Context triple: [Eurojet EJ200, instanceOf, military aircraft engine]
-
A.
military aircraft
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
B.
aircraft piston engine
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.
-
C.
twin‑engine aircraft
A twin-engine aircraft is an airplane equipped with two engines, typically mounted on the wings or fuselage, providing increased power, redundancy, and safety compared to single-engine designs.
-
D.
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.
-
E.
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.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.