Triple
T29662393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fenestron |
E750445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | helicopter tail rotor system |
C56044
|
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: helicopter tail rotor system Context triple: [Fenestron, instanceOf, helicopter tail rotor system]
-
A.
tandem-rotor helicopter
A tandem-rotor helicopter is a rotary-wing aircraft featuring two large horizontal rotors mounted one in front of the other, rotating in opposite directions to provide lift and directional control without the need for a tail rotor.
-
B.
helicopter powerplant
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.
-
C.
piston-powered helicopter
A piston-powered helicopter is a rotary-wing aircraft whose main rotor is driven by one or more reciprocating (piston) engines, typically used for light-duty, training, or private operations due to their lower cost and complexity compared to turbine-powered helicopters.
-
D.
turbine-powered helicopter
A turbine-powered helicopter is a rotary-wing aircraft that uses one or more gas-turbine engines to drive its main and tail rotors, providing lift, thrust, and control.
-
E.
twin-engine helicopter
A twin-engine helicopter is a rotary-wing aircraft equipped with two independent engines that provide increased power, redundancy, and safety for missions such as transport, search and rescue, and offshore operations.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 6:59 p.m.