Triple

T30887367
Position Surface form Disambiguated ID Type / Status
Subject YC-97B E786803 entity
Predicate instanceOf P0 FINISHED
Object Boeing C-97 Stratofreighter variant C57723 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 C-97 Stratofreighter variant
Context triple: [YC-97B, instanceOf, Boeing C-97 Stratofreighter variant]
  • A. Boeing C-97 Stratofreighter variant chosen
    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.
  • B. Boeing B-17 variant
    A Boeing B-17 variant is a specific model or modification of the B-17 Flying Fortress bomber, distinguished by changes in design, equipment, performance, or mission role.
  • C. Boeing B-50 Superfortress
    The Boeing B-50 Superfortress was a post–World War II American strategic bomber, an improved derivative of the B-29 with more powerful engines and structural enhancements, used primarily for long-range nuclear deterrence and reconnaissance in the early Cold War.
  • D. 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.
  • E. variant of Douglas C-47 Skytrain
    A variant of the Douglas C-47 Skytrain is a specific modified version of this military transport aircraft, distinguished by changes in equipment, configuration, or performance to fulfill specialized operational roles.
  • 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_69f224bbfa7c81908448e0c261c523e3 completed April 29, 2026, 3:33 p.m.
Created at: April 29, 2026, 8:49 p.m.