Triple

T14982795
Position Surface form Disambiguated ID Type / Status
Subject Trident 2E E373621 entity
Predicate instanceOf P0 FINISHED
Object Hawker Siddeley Trident variant C35360 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 Trident variant
Context triple: [Trident 2E, instanceOf, Hawker Siddeley Trident variant]
  • A. 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.
  • B. Handley Page Halifax variant
    A Handley Page Halifax variant is a specific model or modification of the British four‑engined heavy bomber, distinguished by changes in engines, armament, structure, or equipment to fulfill particular operational roles during its service life.
  • C. 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.
  • D. Gloster Meteor variant
    A Gloster Meteor variant is a specific model or modification of the original British twin‑jet fighter, distinguished by changes in design, equipment, or role to meet particular operational requirements.
  • E. Avro Vulcan
    The Avro Vulcan is a British delta-wing strategic bomber developed in the 1950s, renowned for its distinctive shape, nuclear deterrent role during the Cold War, and later use in long-range conventional bombing missions.
  • 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_69d85ccbbcd48190acb56e7cf104d8ad completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 2:52 a.m.