Triple
T8225157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addis Ababa Action Agenda on financing for development |
E192157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental consensus |
C23720
|
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: intergovernmental consensus Context triple: [Addis Ababa Action Agenda on financing for development, instanceOf, intergovernmental consensus]
-
A.
intergovernmental partnership
An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
-
B.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
C.
intergovernmental platform
An intergovernmental platform is a structured forum or mechanism through which multiple governments collaborate, coordinate policies, share information, and make joint decisions on issues of common interest.
-
D.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
E.
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.
- F. None of above. chosen
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_69ca82c9a8ac81908b011c38698456e4 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:45 p.m.