Triple
T16864052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Elveden |
E409992
|
entity |
| Predicate | notableArrests |
P125272
|
FINISHED |
| Object | Sun journalists |
—
|
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: Sun journalists | Statement: [Operation Elveden, notableArrests, Sun journalists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableArrests Context triple: [Operation Elveden, notableArrests, Sun journalists]
-
A.
notableArrestee
Indicates that the subject is a person who was arrested in a way considered notable or significant, typically in connection with the object (such as an event, case, or authority).
-
B.
arrests
Indicates that one entity, typically an authority figure, seizes and detains another entity under legal or official power.
-
C.
notablePrisoner
Indicates that a person is recognized as a significant or noteworthy inmate of a particular prison or detention facility.
-
D.
notablePrison
Indicates that an entity is a prison of particular significance or prominence in relation to another entity.
-
E.
notablePrisonerGuarded
Indicates that a guard was responsible for overseeing or guarding a prisoner who is considered notable or significant.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b505a390819097ec31cd210eca60 |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.