Triple
T17358091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrean–Djiboutian border |
E421993
|
entity |
| Predicate | hasCeasefireAgreement |
P40461
|
FINISHED |
| Object | Qatar-mediated agreement |
—
|
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: Qatar-mediated agreement | Statement: [Eritrean–Djiboutian border, hasCeasefireAgreement, Qatar-mediated agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCeasefireAgreement Context triple: [Eritrean–Djiboutian border, hasCeasefireAgreement, Qatar-mediated agreement]
-
A.
hasCeasefire
chosen
Indicates that a formal agreement has been established to temporarily stop hostilities or armed conflict between the involved parties.
-
B.
ceasefireDeclared
Indicates that a formal agreement has been made to stop hostilities or armed conflict between opposing parties.
-
C.
ceasefireSignedBy
Indicates that a formal ceasefire agreement has been signed by the specified party or parties.
-
D.
hasCeasefireHistoryWith
Indicates that two parties have previously been involved together in one or more ceasefire agreements or periods of formally suspended hostilities.
-
E.
endedCeasefire
Indicates that a previously established ceasefire between parties has been terminated or broken.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a4a37788190b330b7207aa424b6 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.