Triple
T21694906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centre for Data Protection |
E535477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data protection body |
C29328
|
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: data protection body Context triple: [Centre for Data Protection, instanceOf, data protection body]
-
A.
data protection authority coordination body
A data protection authority coordination body is an entity that facilitates cooperation, information-sharing, and consistent decision-making among multiple data protection authorities across regions or jurisdictions.
-
B.
data management body
chosen
A data management body is an organized group or authority responsible for establishing, overseeing, and enforcing policies, standards, and practices for the collection, storage, use, and protection of data within an organization or jurisdiction.
-
C.
data protection solution
A data protection solution is a system or set of tools and practices designed to safeguard data from loss, corruption, unauthorized access, and misuse throughout its lifecycle.
-
D.
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.
-
E.
risk and compliance data service
A risk and compliance data service aggregates, analyzes, and delivers regulatory, risk, and compliance-related information to help organizations identify exposures, meet legal obligations, and support informed governance decisions.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:45 p.m.