Triple

T34066226
Position Surface form Disambiguated ID Type / Status
Subject HS 125 Series 400 E873632 entity
Predicate instanceOf P0 FINISHED
Object Hawker Siddeley HS 125 variant C58441 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 Siddeley HS 125 variant
Context triple: [HS 125 Series 400, instanceOf, Hawker Siddeley HS 125 variant]
  • A. Hawker Siddeley HS 125 variant chosen
    A Hawker Siddeley HS 125 variant is a specific model within the HS 125 family of British twin-engine mid-size business jets, distinguished by particular design, performance, or avionics modifications.
  • B. 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.
  • C. Hawker Tempest variant
    A Hawker Tempest variant is a specific model or sub-type of the British Hawker Tempest fighter aircraft distinguished by particular design features, performance characteristics, or operational roles.
  • D. Rolls-Royce Avon variant
    The Rolls-Royce Avon variant is a specific model within the Avon family of axial-flow turbojet engines, distinguished by tailored performance characteristics, configurations, or applications for particular aircraft or operational requirements.
  • E. Panavia Tornado variant
    A Panavia Tornado variant is a specific model of the multirole combat aircraft tailored with distinct avionics, structural modifications, and mission equipment to fulfill specialized roles such as strike, reconnaissance, or air defense.
  • 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_69f349a4af208190afa14888f9c9fb9d completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:52 a.m.