Triple

T9804876
Position Surface form Disambiguated ID Type / Status
Subject NATO air traffic control structures E237930 entity
Predicate instanceOf P0 FINISHED
Object military command and control system C23791 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 command and control system
Context triple: [NATO air traffic control structures, instanceOf, military command and control system]
  • A. maritime command and control framework
    A maritime command and control framework is an integrated structure of processes, technologies, and organizational roles that enables coordinated planning, decision-making, and execution of naval and maritime operations across multiple domains and stakeholders.
  • B. command-and-control framework chosen
    A command-and-control framework is a structured system that enables centralized coordination, tasking, and monitoring of distributed agents or components, often used to manage operations, automation, or cyber activities.
  • C. military system
    A military system is an organized structure of personnel, equipment, doctrines, and processes designed to plan, conduct, and support defense and combat operations.
  • D. deployable air command and control centre
    A deployable air command and control centre is a mobile, rapidly configurable facility that provides the infrastructure, systems, and personnel needed to plan, direct, and coordinate air operations in a given theater.
  • E. 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.
  • 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_69ca84dd4608819097ff4ed00feca280 completed March 30, 2026, 2:12 p.m.
Created at: March 30, 2026, 8:29 p.m.