Triple
T33411321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTM322-01/9 |
E855590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | turboshaft engine variant |
C32607
|
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: turboshaft engine variant Context triple: [RTM322-01/9, instanceOf, turboshaft engine variant]
-
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.
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.
-
C.
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.
-
D.
Rolls-Royce Olympus variant
A Rolls-Royce Olympus variant is a specific model within the Olympus family of axial-flow turbojet or turbofan engines, distinguished by tailored design modifications to meet particular aircraft, marine, or industrial performance and installation requirements.
-
E.
helicopter powerplant
chosen
A helicopter powerplant is the integrated system of engines and associated components that generate and transmit power to drive the helicopter’s rotors and onboard systems.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.