Triple
T10513364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GFMD |
E247971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental process |
C9247
|
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 process Context triple: [GFMD, instanceOf, intergovernmental process]
-
A.
intergovernmental programme
An intergovernmental programme is a coordinated set of policies, activities, or initiatives jointly designed, funded, and implemented by multiple governments or international organizations to address shared issues or achieve common goals across borders.
-
B.
intergovernmental consensus
Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
-
C.
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.
-
D.
intergovernmental platform
chosen
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.
-
E.
United Nations intergovernmental process
The United Nations intergovernmental process is the formal, member state–driven system of negotiations, decision-making, and norm-setting through which UN bodies develop, adopt, and implement international agreements, resolutions, and policies.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:27 p.m.