Triple
T32517956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multistakeholder Advisory Group |
E831107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multistakeholder body |
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: multistakeholder body Context triple: [Multistakeholder Advisory Group, instanceOf, multistakeholder body]
-
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.
non-governmental public body
A non-governmental public body is an organization that, while independent of direct government control, performs functions or provides services of public interest, often operating under public law or with public funding and oversight.
-
C.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or 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.
secretariat-type body
A secretariat-type body is an administrative organization that provides ongoing coordination, support, and implementation services for a larger governing or decision-making entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.