Triple
T16864055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Elveden |
E409992
|
entity |
| Predicate | chargesBrought |
P1779
|
FINISHED |
| Object | misconduct in public office |
—
|
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: misconduct in public office | Statement: [Operation Elveden, chargesBrought, misconduct in public office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargesBrought Context triple: [Operation Elveden, chargesBrought, misconduct in public office]
-
A.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
B.
chargeOnChief
Indicates that a formal accusation or legal charge is filed against a chief or primary authority figure.
-
C.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
D.
chargedOn
Indicates that a fee, cost, or financial amount is applied to an account, entity, or transaction at a specific time or in connection with a particular event.
-
E.
legalCharge
chosen
Indicates that an authority has formally accused an entity of committing a specific legal offense or violation.
- 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_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. |
Created at: April 10, 2026, 5:24 a.m.