Triple

T27749119
Position Surface form Disambiguated ID Type / Status
Subject Semi-Automatic Ground Environment E702069 entity
Predicate instanceOf P0 FINISHED
Object computer-based command and control system C32756 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: computer-based command and control system
Context triple: [Semi-Automatic Ground Environment, instanceOf, computer-based command and control system]
  • A. missile defense command and control system
    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.
  • B. command and control centre
    A command and control centre is a centralized facility where information is collected, analyzed, and used to coordinate and direct operations, resources, and decision-making in real time.
  • C. command and control structure
    A command and control structure is an organizational framework that defines how authority, decision-making, and information flow are coordinated to direct and manage operations toward specific objectives.
  • D. command-and-control facility chosen
    A command-and-control facility is a secure, centralized location equipped with communication, monitoring, and decision-support systems used to direct and coordinate operations and resources in real time.
  • E. command and control activity
    A command and control activity is an operation or process through which authority is exercised to direct, coordinate, and manage resources and actions toward achieving specific objectives.
  • 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_69ef6a53c7388190899baa6daf42301c completed April 27, 2026, 1:53 p.m.
Created at: April 27, 2026, 4:18 p.m.