Triple
T28479953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bölkow Bo‑102 Helitrainer |
E720664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rotorcraft training device |
C41105
|
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: rotorcraft training device Context triple: [Bölkow Bo‑102 Helitrainer, instanceOf, rotorcraft training device]
-
A.
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.
-
B.
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.
-
C.
rotorcraft lander
A rotorcraft lander is a vertical-takeoff-and-landing spacecraft or planetary probe that uses powered rotors instead of rockets or wings to descend, land, and maneuver near a surface.
-
D.
military training helicopter
chosen
A military training helicopter is a rotary-wing aircraft specifically designed or adapted to teach pilots and aircrew fundamental and advanced flight, navigation, and mission skills in a controlled training environment.
-
E.
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.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:54 a.m.