Triple
T9153525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Public Meetings |
E219648
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multistakeholder governance forum |
C10752
|
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 governance forum Context triple: [ICANN Public Meetings, instanceOf, multistakeholder governance forum]
-
A.
multistakeholder organization
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.
civil society forum
A civil society forum is a structured platform where non-governmental organizations, community groups, and citizens convene to discuss public issues, influence policy, and coordinate collective action.
-
C.
convening platform
chosen
A convening platform is a structured environment—physical, digital, or hybrid—that brings diverse stakeholders together to connect, collaborate, and coordinate around shared goals or issues.
-
D.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
E.
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.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:20 p.m.