Triple
T38323852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPA 2006 |
E1036728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Comprehensive 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: Comprehensive Peace Accord Context triple: [CPA 2006, instanceOf, Comprehensive Peace Accord]
-
A.
Sudanese political agreement
A Sudanese political agreement is a formal accord between Sudanese political actors or factions that outlines shared principles, power arrangements, and mechanisms for governance, conflict resolution, or transition.
-
B.
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.
-
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, address global issues, or establish cooperative frameworks under international law.
-
D.
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.
-
E.
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.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.