Triple
T36467023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC‑CY |
E898448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybercrime policy body |
C27762
|
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: cybercrime policy body Context triple: [PC‑CY, instanceOf, cybercrime policy body]
-
A.
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.
-
B.
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.
-
C.
criminal justice policy advisory body
chosen
A criminal justice policy advisory body is a group of experts and stakeholders that analyzes data, evaluates existing practices, and provides recommendations to guide the development, reform, and implementation of criminal justice laws and policies.
-
D.
security sector reform body
A security sector reform body is an organization or institutional mechanism responsible for planning, coordinating, and overseeing changes to a country’s security institutions—such as the military, police, and intelligence services—to make them more effective, accountable, and aligned with democratic norms and human rights.
-
E.
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.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.