Triple
T31056614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPA 2018 |
E791413
|
entity |
| Predicate | hasDataSubjectRight |
P172855
|
FINISHED |
| Object | right of access |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: right of access | Statement: [DPA 2018, hasDataSubjectRight, right of access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataSubjectRight Context triple: [DPA 2018, hasDataSubjectRight, right of access]
-
A.
hasDataProtectionAuthority
Indicates that an entity is subject to, overseen by, or associated with a specific data protection authority responsible for regulating its handling of personal data.
-
B.
hasGivenConsentFor
Indicates that one entity has granted permission or approval for a specific action, process, or use involving another entity or resource.
-
C.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
D.
dataSubject
Indicates that one entity is the individual to whom the personal data or information in question relates.
-
E.
dataAccessibleTo
Indicates that certain data can be reached, retrieved, or used by a specified entity or system.
- F. None of above. chosen
Provenance (4 batches)
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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 29, 2026, 9 p.m.