Triple
T29383210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonn Powers |
E745186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-conflict governance mechanism |
C11952
|
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: post-conflict governance mechanism Context triple: [Bonn Powers, instanceOf, post-conflict governance mechanism]
-
A.
civil conflict
Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
-
B.
peace and security architecture
A peace and security architecture is an integrated system of institutions, norms, mechanisms, and processes designed to prevent conflict, manage crises, and sustain long-term stability within and among states.
-
C.
party-led governance mechanism
A party-led governance mechanism is a system in which a political party, rather than independent state institutions or pluralistic competition, directs and coordinates key decision-making, policy implementation, and oversight across government and society.
-
D.
peace commission
chosen
A peace commission is an official body established to investigate conflicts, promote dialogue, and recommend measures to prevent, resolve, or reconcile disputes between parties.
-
E.
peacekeeping support mechanism
A peacekeeping support mechanism is a structured system of resources, processes, and coordination tools designed to assist, sustain, and enhance the effectiveness of peacekeeping operations in preventing, managing, and resolving conflicts.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:36 p.m.