Triple

T36626817
Position Surface form Disambiguated ID Type / Status
Subject Buccaneer S.1 E904197 entity
Predicate instanceOf P0 FINISHED
Object carrier-based strike aircraft variant C28933 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: carrier-based strike aircraft variant
Context triple: [Buccaneer S.1, instanceOf, carrier-based strike aircraft variant]
  • A. carrier-based strike aircraft chosen
    A carrier-based strike aircraft is a naval combat airplane designed to operate from aircraft carriers and conduct precision attacks against surface, land, and maritime targets.
  • B. navalized aircraft variant
    A navalized aircraft variant is a modified version of a land-based aircraft adapted for operation from naval vessels, typically featuring structural reinforcement, corrosion protection, carrier-landing gear, and maritime avionics.
  • C. maritime patrol aircraft variant
    A maritime patrol aircraft variant is a specialized version of an aircraft configured and equipped for long-endurance surveillance, anti-submarine warfare, and maritime security operations over sea areas.
  • D. fighter-bomber aircraft variant
    A fighter-bomber aircraft variant is a modified version of a base aircraft optimized to perform both air-to-air combat and ground-attack missions through changes in avionics, weapons systems, and structural configuration.
  • E. fixed-wing aircraft carrier
    A fixed-wing aircraft carrier is a large naval warship designed with a full-length flight deck and specialized facilities to launch, recover, and support fixed-wing aircraft operations at sea.
  • 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_69f76e6ae750819096911e6e2d4d12c5 completed May 3, 2026, 3:48 p.m.
Created at: May 3, 2026, 4:11 p.m.