Triple
T28554553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Cyber Directorate |
E722969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national cyber security authority |
C9230
|
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: national cyber security authority Context triple: [National Cyber Directorate, instanceOf, national cyber security authority]
-
A.
national security authority
A national security authority is a governmental body responsible for safeguarding a nation’s security interests by overseeing intelligence, defense coordination, threat assessment, and the protection of critical assets and information.
-
B.
cybersecurity agency
chosen
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
C.
cybersecurity coordination body
A cybersecurity coordination body is an organization that facilitates collaboration, information sharing, and joint response among stakeholders to prevent, detect, and mitigate cyber threats.
-
D.
national central agency
A national central agency is a government body that coordinates, regulates, and oversees specific functions or policies at the national level, often serving as the primary authority and point of contact for those activities.
-
E.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:44 a.m.