Triple

T14505943
Position Surface form Disambiguated ID Type / Status
Subject European Data Protection Board E340263 entity
Predicate instanceOf P0 FINISHED
Object data protection authority coordination body C34873 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 authority coordination body
Context triple: [European Data Protection Board, instanceOf, data protection authority coordination 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. data management body
    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. intelligence coordination body
    An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security objectives.
  • D. financial regulatory coordination body
    A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
  • E. coordination office
    A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
  • F. None of above. chosen

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_69d822d9c0408190b9a2b3643e58bb4d completed April 9, 2026, 10:06 p.m.
Created at: April 10, 2026, 1:21 a.m.