Triple
T11059048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lusaka Protocol |
E261456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Angolan peace 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: Angolan peace accord Context triple: [Lusaka Protocol, instanceOf, Angolan peace accord]
-
A.
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.
-
B.
United Nations–brokered accord
A United Nations–brokered accord is a formal agreement between parties, typically states or factions, negotiated and facilitated by the UN to resolve conflicts, address global issues, or establish cooperative frameworks under international law.
-
C.
United Nations–brokered accord
A United Nations–brokered accord is a formal agreement between parties, typically states or factions, negotiated and facilitated by the UN to resolve conflicts, manage disputes, or establish cooperative frameworks under international oversight.
-
D.
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.
-
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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.