Triple
T6807507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omagh |
E156344
|
entity |
| Predicate | bombingInjuries |
P1399
|
FINISHED |
| Object | hundreds injured |
—
|
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: hundreds injured | Statement: [Omagh, bombingInjuries, hundreds injured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombingInjuries Context triple: [Omagh, bombingInjuries, hundreds injured]
-
A.
resultOfBombing
Indicates that something exists or occurs as a consequence or outcome of a bombing event.
-
B.
bombed
Indicates that one entity attacked another using explosive weapons, causing or intending to cause destruction or damage.
-
C.
casualties
chosen
Indicates that an event, action, or situation resulted in people being killed or injured.
-
D.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
E.
numberOfPeopleKilledInBombing
Indicates the total count of people who were killed as a direct result of a specific bombing event.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30a006081908996e31aa7ced0ac |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.