Triple
T9314499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data Protection Act 2018 |
E224083
|
entity |
| Predicate | requires |
P100
|
FINISHED |
| Object | data protection impact assessments in certain cases |
—
|
LITERAL 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.
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: data protection impact assessments in certain cases | Statement: [Data Protection Act 2018, requires, data protection impact assessments in certain cases]
Provenance (2 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
Created at: March 30, 2026, 7:37 p.m.