Triple
T34690815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky Hoverfly |
E890886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikorsky R-4 variant |
C60229
|
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: Sikorsky R-4 variant Context triple: [Sikorsky Hoverfly, instanceOf, Sikorsky R-4 variant]
-
A.
Cessna T‑41 variant
The Cessna T‑41 variant is a military training and liaison aircraft derived from the Cessna 172, adapted with specialized avionics and equipment for pilot instruction and utility roles.
-
B.
Bell 206 variant
A Bell 206 variant is a specific model within the Bell 206 family of light, twin-blade helicopters that incorporates distinct modifications in design, performance, or equipment to fulfill particular operational roles or requirements.
-
C.
Lockheed Model 10 Electra variant
A Lockheed Model 10 Electra variant is a specific configuration of the twin‑engine, all‑metal monoplane airliner distinguished by modifications in equipment, performance, or role (such as transport, survey, or military use) from the standard Model 10 design.
-
D.
de Havilland Canada DHC-1 Chipmunk
The de Havilland Canada DHC-1 Chipmunk is a post-World War II, two-seat, single-engine primary trainer aircraft renowned for its excellent handling and aerobatic capabilities, widely used by military and civilian operators.
-
E.
Convair 240 variant
A Convair 240 variant is a specific model within the Convair 240 family of twin‑engine, short- to medium-range airliners that incorporates design modifications or performance improvements over the original baseline aircraft.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:05 a.m.