Triple
T5426794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Cyber Defence Force |
E121382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyber defence organization |
C300
|
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: cyber defence organization Context triple: [Norwegian Cyber Defence Force, instanceOf, cyber defence organization]
-
A.
cybersecurity agency
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
B.
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.
-
C.
component of the Cybersecurity and Infrastructure Security Agency
A component of the Cybersecurity and Infrastructure Security Agency is an organizational unit or program within CISA that carries out specific cybersecurity, infrastructure protection, emergency communications, or risk management functions in support of the agency’s mission.
-
D.
defense organization
chosen
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
E.
cooperative security activity
A cooperative security activity is a coordinated effort among multiple actors—such as states, organizations, or agencies—to jointly prevent, mitigate, or respond to security threats through shared information, resources, and actions.
- 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.