Triple
T2947274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Integrated Air Defense System |
E79532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military command and control network |
C409
|
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 network Context triple: [NATO Integrated Air Defense System, instanceOf, military command and control network]
-
A.
military communications organization
chosen
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
-
B.
space communication network
A space communication network is an interconnected system of ground stations, satellites, and relay nodes that enables the reliable transmission, routing, and reception of data across space and between space-based and terrestrial assets.
-
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.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
E.
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.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:57 p.m.