Triple
T13133289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dublin |
E312017
|
entity |
| Predicate | antiTreatyFactionGoal |
P108347
|
FINISHED |
| Object | establishment of a full Irish Republic |
—
|
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: establishment of a full Irish Republic | Statement: [Battle of Dublin, antiTreatyFactionGoal, establishment of a full Irish Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antiTreatyFactionGoal Context triple: [Battle of Dublin, antiTreatyFactionGoal, establishment of a full Irish Republic]
-
A.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
C.
brokeTreatyWith
Indicates that one party violated the terms of a formal agreement or treaty it had with another party.
-
D.
archenemyOf
Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
-
E.
weakenedFaction
Indicates that one faction has reduced the strength, influence, or effectiveness of another faction.
- F. None of above. chosen
Provenance (4 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981b3d72c8190b69ae56435a954fa |
completed | April 10, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69d9804543cc8190a23cd7da59a12a7b |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 9:08 p.m.