Triple
T872120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulster Volunteer Force |
E18835
|
entity |
| Predicate | announcedCeasefire |
P21107
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Ulster Volunteer Force, announcedCeasefire, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedCeasefire Context triple: [Ulster Volunteer Force, announcedCeasefire, 1994]
-
A.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
B.
concludedWar
Indicates that a war or armed conflict between entities has come to an end, typically through victory, surrender, or formal agreement.
-
C.
peaceProcessInvolved
Indicates that an entity participates in, contributes to, or is otherwise involved in a formal peace process or peace negotiations.
-
D.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
E.
maintainedPeaceWith
Indicates that two entities sustained a state of peace or non-conflict with each other over a period of time.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac96850881908a2d776685126137 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4abb157d08190a7d7281eb3f1b788 |
completed | March 1, 2026, 9:12 p.m. |
Created at: March 1, 2026, 7:39 p.m.