Triple

T24137350
Position Surface form Disambiguated ID Type / Status
Subject Boeing Fortress I E598125 entity
Predicate instanceOf P0 FINISHED
Object Boeing B-17 variant C48303 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 B-17 variant
Context triple: [Boeing Fortress I, instanceOf, Boeing B-17 variant]
  • A. 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.
  • B. 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.
  • C. Lockheed Constellation variant
    A Lockheed Constellation variant is a specific model within the Constellation family of four‑engined, propeller‑driven airliners and military transports, distinguished by particular structural, performance, or role-related modifications.
  • D. Dornier Do 17 variant
    A Dornier Do 17 variant is a specific model or modification of the German twin-engine light bomber/reconnaissance aircraft, distinguished by changes in structure, equipment, or performance tailored to particular operational roles during its service life.
  • E. Boeing 747 variant
    A Boeing 747 variant is a specific model or configuration of the Boeing 747 airliner, distinguished by differences in size, range, engines, avionics, or interior layout tailored to particular airline or mission requirements.
  • 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_69e288c92e448190ac57034fa0c863ce completed April 17, 2026, 7:23 p.m.
Created at: April 17, 2026, 11:27 p.m.