Triple
T32594907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YC-14A |
E833175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Boeing YC-14 prototype |
C58884
|
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: Boeing YC-14 prototype Context triple: [YC-14A, instanceOf, Boeing YC-14 prototype]
-
A.
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.
-
B.
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.
-
C.
McDonnell Douglas aircraft
McDonnell Douglas aircraft are a family of commercial and military airplanes known for their distinctive designs, such as the DC-9/MD-80 series and F-15 fighter, produced by the former American aerospace manufacturer McDonnell Douglas before its merger with Boeing.
-
D.
McDonnell F-101 Voodoo variant
A McDonnell F-101 Voodoo variant is a specific model within the F-101 family of supersonic jet fighters and reconnaissance aircraft, distinguished by particular modifications in role, avionics, armament, or structural configuration.
-
E.
Boeing C-97 Stratofreighter variant
A Boeing C-97 Stratofreighter variant is a specific model derived from the original C-97 military transport aircraft, modified for specialized roles such as aerial refueling, passenger transport, or other mission-specific purposes.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.