Triple

T24812133
Position Surface form Disambiguated ID Type / Status
Subject SA-6 Gainful E620818 entity
Predicate instanceOf P0 FINISHED
Object mobile air defense system C17786 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: mobile air defense system
Context triple: [SA-6 Gainful, instanceOf, mobile air defense system]
  • A. self-propelled surface-to-air missile system chosen
    A self-propelled surface-to-air missile system is a mobile, ground-based weapons platform that integrates its own propulsion, radar, and missile launch capabilities to detect, track, and engage airborne targets.
  • B. ground-based air defense system
    A ground-based air defense system is a coordinated set of land-deployed sensors, command-and-control elements, and weapon platforms designed to detect, track, and engage airborne threats such as aircraft, missiles, and drones.
  • C. integrated air defence system
    An integrated air defence system is a coordinated network of sensors, command and control elements, and weapon systems designed to detect, track, and engage aerial threats to protect designated airspace and assets.
  • D. surface-to-air missile
    A surface-to-air missile is a guided weapon launched from the ground or sea designed to detect, track, and destroy airborne targets such as aircraft, drones, or other missiles.
  • E. defensive avionics system
    A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
  • 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_69e2fabfd4648190bd0e5c7f4dbb6cab completed April 18, 2026, 3:30 a.m.
Created at: April 18, 2026, 4:50 a.m.