Triple
T10117701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO cyber structures |
E223204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military cyber defence framework |
C20031
|
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 defence framework Context triple: [NATO cyber structures, instanceOf, military cyber defence framework]
-
A.
command-and-control framework
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.
-
B.
security management framework
chosen
A security management framework is a structured set of policies, processes, roles, and controls that organizations use to systematically identify, assess, manage, and monitor security risks to their information and assets.
-
C.
cybersecurity system
A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
-
D.
military leadership framework
A military leadership framework is a structured model that defines the principles, competencies, behaviors, and decision-making processes required to effectively lead individuals and units in military operations and organizational contexts.
-
E.
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.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 9:04 p.m.