Triple
T28388458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIS |
E719085
|
entity |
| Predicate | dataProtectionOversightBy |
P38363
|
FINISHED |
| Object | European Data Protection Supervisor |
—
|
NE NERFINISHED |
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: European Data Protection Supervisor | Statement: [EIS, dataProtectionOversightBy, European Data Protection Supervisor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProtectionOversightBy Context triple: [EIS, dataProtectionOversightBy, European Data Protection Supervisor]
-
A.
hasDataProtectionAuthority
chosen
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.
hasSecurityOversightBy
Indicates that the security responsibilities, controls, or governance for one entity are overseen, managed, or supervised by another entity.
-
C.
oversightTools
Indicates that certain tools or mechanisms are used to monitor, review, or supervise the actions or performance of an entity.
-
D.
dataProtectionFeature
Indicates a feature or mechanism designed to safeguard data from unauthorized access, alteration, loss, or misuse.
-
E.
dataSegregation
Indicates that data is kept separate or partitioned so that information from one group, context, or user is not mixed or accessible with that of another.
- F. None of above.
Provenance (3 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:11 a.m.