Triple
T37556642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen Programme of Action |
E933714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UN action plan |
C23719
|
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: UN action plan Context triple: [Copenhagen Programme of Action, instanceOf, UN action plan]
-
A.
global action plan
A global action plan is a coordinated, strategic framework that outlines shared goals, responsibilities, timelines, and resources for addressing worldwide challenges across nations and organizations.
-
B.
United Nations proposal
A United Nations proposal is a formal document submitted by member states or UN bodies that outlines recommended actions, policies, or resolutions for consideration, negotiation, and potential adoption by UN organs.
-
C.
intergovernmental action plan
An intergovernmental action plan is a coordinated framework of policies, objectives, and implementation steps jointly developed and agreed upon by multiple governments to address shared issues or goals across jurisdictions.
-
D.
United Nations outcome document
chosen
A United Nations outcome document is a formal, negotiated text adopted by UN member states that records agreed conclusions, commitments, and recommended actions resulting from a UN conference, summit, or meeting.
-
E.
United Nations strategic planning framework
The United Nations strategic planning framework is a structured, organization-wide approach that aligns UN mandates, goals, resources, and performance measures to guide coherent, long-term action across agencies and member 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.