Triple

T11897366
Position Surface form Disambiguated ID Type / Status
Subject Command and Control, Battle Management, and Communications (C2BMC) system E283069 entity
Predicate instanceOf P0 FINISHED
Object missile defense command and 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: missile defense command and control system
Context triple: [Command and Control, Battle Management, and Communications (C2BMC) system, instanceOf, missile defense command and control system]
  • A. missile defense program
    A missile defense program is an organized system of technologies, policies, and operations designed to detect, track, intercept, and neutralize incoming missiles before they reach their intended targets.
  • B. air and missile defense interceptor
    An air and missile defense interceptor is a guided weapon system designed to detect, track, and destroy incoming aircraft, cruise missiles, or ballistic missiles before they reach their targets.
  • C. missile defense radar
    A missile defense radar is a specialized sensor system that detects, tracks, and characterizes incoming missiles to support timely interception and defense actions.
  • D. missile warning system
    A missile warning system is a defense mechanism that detects, tracks, and alerts relevant entities to incoming missile threats to enable timely protective or countermeasure responses.
  • E. coastal defense missile system
    A coastal defense missile system is a land-based military installation designed to detect, track, and engage hostile naval targets approaching a nation's shoreline using guided missiles and integrated sensor networks.
  • 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
Created at: April 8, 2026, 9:44 p.m.