Triple
T5535449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish Rebellion of 1803 |
E145149
|
entity |
| Predicate | hasBattleOrAction |
P26893
|
FINISHED |
| Object | attack on Dublin Castle |
—
|
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: attack on Dublin Castle | Statement: [Irish Rebellion of 1803, hasBattleOrAction, attack on Dublin Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBattleOrAction Context triple: [Irish Rebellion of 1803, hasBattleOrAction, attack on Dublin Castle]
-
A.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
-
B.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
C.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
D.
hasSubBattle
chosen
Indicates that a larger battle or conflict includes a smaller, constituent battle as part of its overall engagement.
-
E.
sawCombat
Indicates that an entity directly participated in active military or armed conflict.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01faed1d08190b6a57faedaf1b56a |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.