Triple
T37776036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breguet-Richet Gyroplane |
E941689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | experimental rotary-wing aircraft |
C6075
|
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: experimental rotary-wing aircraft Context triple: [Breguet-Richet Gyroplane, instanceOf, experimental rotary-wing aircraft]
-
A.
experimental aircraft
chosen
An experimental aircraft is a prototype or testbed airplane designed and operated to evaluate new aerodynamic concepts, materials, systems, or technologies outside standard certified production models.
-
B.
rotary-wing UAV
A rotary-wing UAV is an unmanned aerial vehicle that generates lift and maneuverability using one or more powered rotating wings or rotors, enabling vertical takeoff, landing, and hovering.
-
C.
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.
-
D.
rotorcraft development program
A rotorcraft development program is an organized, multi-phase effort to design, test, certify, and field new or improved rotary-wing aircraft to meet specified performance, safety, and mission requirements.
-
E.
tiltrotor aircraft
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.
- 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.