Triple

T22300695
Position Surface form Disambiguated ID Type / Status
Subject Beechcraft Baron 55 E551245 entity
Predicate instanceOf P0 FINISHED
Object Beechcraft Baron variant C46074 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: Beechcraft Baron variant
Context triple: [Beechcraft Baron 55, instanceOf, Beechcraft Baron variant]
  • A. Hawker 800 variant
    The Hawker 800 variant is a mid-size business jet model within the Hawker 800 series, distinguished by specific performance, avionics, or interior configuration differences tailored to particular operational or customer requirements.
  • B. 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.
  • 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. 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.
  • E. 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.
  • 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_69e11e46c0188190800181a4233f28fe completed April 16, 2026, 5:37 p.m.
Created at: April 16, 2026, 8:41 p.m.