Triple

T31744391
Position Surface form Disambiguated ID Type / Status
Subject Victor B.1 E810229 entity
Predicate instanceOf P0 FINISHED
Object Handley Page Victor variant C59137 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: Handley Page Victor variant
Context triple: [Victor B.1, instanceOf, Handley Page Victor variant]
  • A. 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.
  • B. Armstrong Whitworth Whitley variant
    The Armstrong Whitworth Whitley variant is a specific model or modification of the British twin-engine, long-range heavy bomber aircraft used primarily by the Royal Air Force during the early years of World War II.
  • C. Vickers Wellington variant
    A Vickers Wellington variant is a specific model or modification of the British twin‑engine Wellington bomber, distinguished by changes in equipment, structure, or role to meet particular operational requirements.
  • D. Bristol Blenheim variant
    A Bristol Blenheim variant is a specific model or modification of the British twin‑engine light bomber and reconnaissance aircraft, distinguished by changes in features such as engines, armament, equipment, or airframe configuration.
  • E. 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.
  • 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_69f348e233cc819083b6695f70cd75d8 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:26 p.m.