Triple

T31792486
Position Surface form Disambiguated ID Type / Status
Subject ES-3A Shadow E811507 entity
Predicate instanceOf P0 FINISHED
Object carrier-based electronic reconnaissance aircraft C4000 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 electronic reconnaissance aircraft
Context triple: [ES-3A Shadow, instanceOf, carrier-based electronic reconnaissance aircraft]
  • A. reconnaissance aircraft chosen
    A reconnaissance aircraft is a specialized military or intelligence-gathering airplane designed to observe, monitor, and collect information about enemy forces, terrain, or strategic targets using advanced sensors and surveillance equipment.
  • B. carrier-based strike aircraft
    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.
  • C. Coast Guard aircraft
    A Coast Guard aircraft is a specialized airplane or helicopter used by a nation's coast guard to conduct maritime patrol, search and rescue, law enforcement, and environmental protection missions over coastal and offshore areas.
  • D. 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.
  • E. NOAA aircraft
    NOAA aircraft are specialized research planes operated by the National Oceanic and Atmospheric Administration to collect atmospheric, oceanic, and environmental data for weather forecasting, climate research, and hazard monitoring.
  • 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_69f348e60748819082dcaa7792659803 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 11:39 p.m.