Triple
T25947858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geneva Peacebuilding Platform |
E653886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peacebuilding network |
C10379
|
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: peacebuilding network Context triple: [Geneva Peacebuilding Platform, instanceOf, peacebuilding network]
-
A.
peacebuilding initiative
A peacebuilding initiative is a coordinated set of actions, programs, and policies designed to prevent, reduce, or recover from violent conflict by addressing its root causes and strengthening sustainable, inclusive social and political structures.
-
B.
peacebuilding support entity
chosen
A peacebuilding support entity is an organization or mechanism that provides strategic, technical, financial, and coordination assistance to design, implement, and sustain peacebuilding initiatives in conflict-affected or post-conflict contexts.
-
C.
peacebuilding mission
A peacebuilding mission is an organized, often international effort that supports societies emerging from conflict by strengthening institutions, fostering reconciliation, and promoting sustainable peace.
-
D.
peace promotion role
A peace promotion role is a position or function dedicated to preventing, reducing, or resolving conflict and fostering harmonious, cooperative relationships among individuals, groups, or nations.
-
E.
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.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8:43 a.m.