Triple
T11006930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Privacy Commissioner (New Zealand) |
E260141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | privacy regulator |
C1181
|
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: privacy regulator Context triple: [Office of the Privacy Commissioner (New Zealand), instanceOf, privacy regulator]
-
A.
privacy law
Privacy law is the body of legal rules and principles that governs the collection, use, storage, and disclosure of personal information to protect individuals’ privacy rights.
-
B.
regulatory authority
chosen
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
C.
media regulator
A media regulator is an authority or organization responsible for overseeing and enforcing rules, standards, and policies governing media content, ownership, and distribution to protect the public interest.
-
D.
privacy consent profile
A privacy consent profile is a structured record of an individual’s permissions, preferences, and restrictions regarding the collection, use, and sharing of their personal data across systems and contexts.
-
E.
security advocate
A security advocate is a professional who champions, educates, and influences best practices in security across teams and organizations to reduce risk and promote a strong security culture.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.