Triple
T34989209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vertibird |
E1009334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tilt-rotor aircraft |
C23898
|
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: tilt-rotor aircraft Context triple: [Vertibird, instanceOf, tilt-rotor aircraft]
-
A.
tiltrotor aircraft
chosen
A tiltrotor aircraft is a type of aircraft with rotating engine nacelles or rotors that can tilt between vertical and horizontal positions, enabling both vertical takeoff and landing like a helicopter and efficient forward flight like an airplane.
-
B.
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.
-
C.
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.
-
D.
rotorcraft design
Rotorcraft design is the engineering discipline focused on conceptualizing, analyzing, and optimizing vertical-lift aircraft—such as helicopters and tiltrotors—by integrating aerodynamics, structures, propulsion, controls, and mission requirements.
-
E.
multi‑purpose helicopter
A multi-purpose helicopter is a versatile rotary-wing aircraft designed to perform a wide range of missions—such as transport, search and rescue, surveillance, and support—by accommodating different payloads, equipment, and operating 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.