Triple
T922408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enniskillen bombing |
E19909
|
entity |
| Predicate | primaryVictimGroup |
P699
|
FINISHED |
| Object | people attending a war memorial service |
—
|
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: people attending a war memorial service | Statement: [Enniskillen bombing, primaryVictimGroup, people attending a war memorial service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVictimGroup Context triple: [Enniskillen bombing, primaryVictimGroup, people attending a war memorial service]
-
A.
victimGroup
chosen
Indicates that one group or entity is the target or recipient of harm, abuse, or wrongdoing caused by another.
-
B.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
C.
accusedGroup
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
-
D.
portraysAsVictim
Indicates that one entity represents or depicts another entity as a victim in a given context or narrative.
-
E.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b313cb908190ad78b3a54e4f2eb7 |
completed | March 1, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.