Triple

T19676620
Position Surface form Disambiguated ID Type / Status
Subject U-125A E472468 entity
Predicate instanceOf P0 FINISHED
Object Hawker 800 variant C42331 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: Hawker 800 variant
Context triple: [U-125A, instanceOf, Hawker 800 variant]
  • A. Gulfstream V variant
    A Gulfstream V variant is a specific model or configuration of the long-range, large-cabin Gulfstream V business jet, modified to meet particular performance, mission, or customer requirements.
  • B. Learjet 35 variant
    A Learjet 35 variant is a specific model or modification of the Learjet 35 light business jet, distinguished by changes in performance, configuration, or equipment to suit particular operational roles or customer requirements.
  • C. 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.
  • D. Hawker Siddeley Trident variant
    A Hawker Siddeley Trident variant is a specific model within the Trident family of British-built, three-engined jet airliners, distinguished by particular design modifications, performance characteristics, and operational roles.
  • E. Lockheed L-1011 TriStar variant
    A Lockheed L-1011 TriStar variant is a specific model within the L-1011 widebody trijet family distinguished by particular combinations of engine performance, range, structural modifications, and avionics tailored to different 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_69d8e514f2e08190ba70a4449519d218 completed April 10, 2026, 11:55 a.m.
Created at: April 10, 2026, 1:45 p.m.