Triple
T19951579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballymurphy, Belfast |
E479566
|
entity |
| Predicate | victimsOfNotableEvent |
P35438
|
FINISHED |
| Object | civilians |
—
|
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: civilians | Statement: [Ballymurphy, Belfast, victimsOfNotableEvent, civilians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimsOfNotableEvent Context triple: [Ballymurphy, Belfast, victimsOfNotableEvent, civilians]
-
A.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
B.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
C.
casualtiesAssociatedWithEvent
chosen
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
-
D.
notableDeathTollEvent
Indicates that an event is characterized by causing an unusually large or historically significant number of deaths.
-
E.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a6c87388190a1bada3117acaf7b |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.