Triple
T23628794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETA |
E583548
|
entity |
| Predicate | announcedPermanentCeasefire |
P153334
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [ETA, announcedPermanentCeasefire, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedPermanentCeasefire Context triple: [ETA, announcedPermanentCeasefire, 2011]
-
A.
announcedCeasefire
Indicates that an entity has formally declared the suspension of hostilities or fighting, typically within a conflict or war.
-
B.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
C.
declaredCeasefire
Indicates that one party has formally announced a suspension of hostilities or active conflict with another party.
-
D.
ceasefireEnded
Indicates that a previously established ceasefire between parties has come to an end and hostilities may resume.
-
E.
ceasefireWith
Indicates a mutual agreement between parties to stop hostilities or armed conflict, typically for a specified period or under certain conditions.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e5ae80819085c417e8d81b74ad |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:46 p.m.