Triple
T8370521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Algiers Agreement for Peace and Reconciliation in Mali |
E197440
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ceasefire and political settlement accord |
C22138
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ceasefire and political settlement accord Context triple: [2015 Algiers Agreement for Peace and Reconciliation in Mali, instanceOf, ceasefire and political settlement accord]
-
A.
ceasefire
A ceasefire is a mutually agreed temporary suspension of active hostilities between conflicting parties, typically intended to create conditions for negotiation or humanitarian relief.
-
B.
peace settlement
chosen
A peace settlement is a formal agreement between conflicting parties that ends hostilities and establishes terms for lasting resolution and post-conflict relations.
-
C.
peace negotiation
A peace negotiation is a structured process in which conflicting parties communicate and bargain to reach mutually acceptable agreements that end or reduce violence and establish conditions for lasting peace.
-
D.
truce
A truce is a mutually agreed temporary cessation of hostilities between opposing parties, typically to allow negotiation, humanitarian relief, or a pause in conflict.
-
E.
component of peace accords
A component of peace accords is a distinct provision or mechanism within a negotiated agreement that addresses specific issues—such as security, governance, justice, or reconstruction—to facilitate the resolution of conflict and the establishment of sustainable peace.
- F. None of above.
Provenance (1 batch)
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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:01 p.m.