Triple
T25863211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Cannon |
E651540
|
entity |
| Predicate | eventInvestigated |
P16515
|
FINISHED |
| Object | Manchester city centre bombing |
—
|
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: Manchester city centre bombing | Statement: [Operation Cannon, eventInvestigated, Manchester city centre bombing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventInvestigated Context triple: [Operation Cannon, eventInvestigated, Manchester city centre bombing]
-
A.
investigatedEvent
chosen
Indicates that an event was the subject of an investigation or inquiry carried out by some agent.
-
B.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
C.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
D.
investigatesCase
Indicates that one entity conducts an investigation into a particular case involving events, issues, or individuals.
-
E.
investigationInvolvement
Indicates that an entity participates in, is associated with, or plays a role in a particular investigation.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:06 a.m.