Triple
T6835386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel HeS 011 |
E157436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | axial-flow turbojet |
C14076
|
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: axial-flow turbojet Context triple: [Heinkel HeS 011, instanceOf, axial-flow turbojet]
-
A.
turbofan engine
A turbofan engine is a type of air-breathing jet engine that uses a large fan driven by a gas turbine to produce thrust through both accelerated bypass air and exhaust gases for efficient high-speed propulsion.
-
B.
afterburning turbofan engine
An afterburning turbofan engine is a type of jet engine that combines a turbofan’s efficient core and bypass airflow with an additional combustion stage in the exhaust (afterburner) to provide short-term, significantly increased thrust, typically for military aircraft.
-
C.
gas turbine engine
chosen
A gas turbine engine is a continuous-flow internal combustion engine that compresses air, mixes it with fuel, burns the mixture, and expands the hot gases through turbine and nozzle stages to produce mechanical power or thrust.
-
D.
vectored-thrust jet engine
A vectored-thrust jet engine is a jet propulsion system whose exhaust flow can be mechanically redirected to provide thrust in varying directions, enabling enhanced maneuverability and short or vertical takeoff and landing capabilities.
-
E.
military aircraft engine
A military aircraft engine is a high-performance propulsion system designed to power combat and support aircraft, optimized for thrust, reliability, maneuverability, and operation under extreme conditions.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:19 p.m.