Triple
T32519002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN community |
E831132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-stakeholder community |
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 community Context triple: [ICANN community, instanceOf, multi-stakeholder community]
-
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.
multistakeholder policy
A multistakeholder policy is a governance framework in which decisions are developed and implemented collaboratively by diverse actors—such as governments, private sector, civil society, and technical experts—who share responsibility and influence over outcomes.
-
C.
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.
-
D.
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.
-
E.
transnational community
A transnational community is a network of people who maintain enduring social, economic, political, and cultural ties across national borders, creating a shared sense of belonging that spans multiple countries.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.