Triple
T32997049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Cyber Operations Centre |
E844258
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber command centre |
C41698
|
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 cyber command centre Context triple: [NATO Cyber Operations Centre, instanceOf, military cyber command centre]
-
A.
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.
-
B.
cyberspace operations command
chosen
A cyberspace operations command is a military or governmental organizational entity responsible for planning, directing, and executing offensive, defensive, and support activities within and through cyberspace to achieve strategic and operational objectives.
-
C.
military operations center
A military operations center is a centralized facility where commanders and staff monitor, coordinate, and direct military activities and resources in real time.
-
D.
command-and-control facility
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.
military base network
A military base network is an interconnected system of communication, data, and operational infrastructure linking facilities, units, and resources across one or more military installations to support command, control, logistics, and security functions.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.