Triple
T15146885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Coffee Platform |
E361832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-stakeholder organization |
C999
|
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: multi-stakeholder organization Context triple: [Global Coffee Platform, instanceOf, multi-stakeholder organization]
-
A.
multistakeholder organization
chosen
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
B.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
C.
transnational organization
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
-
D.
stakeholder group
A stakeholder group is a collection of individuals or organizations that share a common interest in, or are affected by, the decisions, activities, or outcomes of a project, organization, or system.
-
E.
international partnership organization
An international partnership organization is a collaborative entity formed by multiple countries, institutions, or stakeholders to coordinate resources, expertise, and policies toward shared global goals and initiatives.
- 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_69d85a0759908190b8a051d2e2a1cbe6 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:07 a.m.