Triple

T34720376
Position Surface form Disambiguated ID Type / Status
Subject Cooperative Engagement Capability E1000896 entity
Predicate instanceOf P0 FINISHED
Object military sensor and fire-control system C30581 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: military sensor and fire-control system
Context triple: [Cooperative Engagement Capability, instanceOf, military sensor and fire-control system]
  • A. weapon system
    A weapon system is an integrated set of components, technologies, and processes designed to detect, engage, and neutralize targets through the controlled application of force.
  • B. missile guidance and control system
    A missile guidance and control system is an integrated set of sensors, processors, and actuators that continuously determines a missile’s position and trajectory and adjusts its flight path to accurately reach a designated target.
  • C. military radar system
    A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
  • D. sensor-fuzed munition
    A sensor-fuzed munition is a smart weapon that disperses multiple submunitions equipped with sensors to detect, identify, and autonomously attack specific targets, such as armored vehicles, within a designated area.
  • E. missile defense command and control system chosen
    A missile defense command and control system is an integrated network of sensors, communication links, decision-support tools, and engagement controls that detects, tracks, evaluates, and coordinates responses to missile threats in real time.
  • 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_69f76dad3f108190a280fd0a2f4ee89a completed May 3, 2026, 3:45 p.m.
Created at: May 3, 2026, 3:59 p.m.