Triple
T34591178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky S-58 design |
E888185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | helicopter airframe design |
C51062
|
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 airframe design Context triple: [Sikorsky S-58 design, instanceOf, helicopter airframe design]
-
A.
helicopter tail rotor system
A helicopter tail rotor system is a mechanical assembly that provides anti-torque and directional control by generating lateral thrust at the tail of the helicopter.
-
B.
helicopter concept
chosen
A helicopter concept is an abstract representation of a rotary-wing aircraft’s essential characteristics, including its structure, propulsion, control systems, and operational capabilities, independent of any specific physical instance.
-
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.
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.
-
E.
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.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.