Triple
T32519004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN community |
E831132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Internet governance actor |
C26498
|
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: Internet governance actor Context triple: [ICANN community, instanceOf, Internet governance actor]
-
A.
Internet governance role
An Internet governance role is a position responsible for shaping, implementing, or overseeing policies, standards, and decision-making processes that affect the operation, security, and evolution of the global internet.
-
B.
Internet governance community
chosen
The Internet governance community is a diverse, multi-stakeholder group of individuals and organizations that collaboratively develop, influence, and implement policies, standards, and practices shaping the global Internet’s operation and evolution.
-
C.
internet governance concept
An internet governance concept is an abstract idea or framework that guides how the internet is managed, regulated, and shaped by technical, legal, economic, and social policies across diverse stakeholders.
-
D.
civil society organizations in Internet governance
Civil society organizations in Internet governance are non-governmental, non-profit groups that represent public interest perspectives, advocate for human rights and digital freedoms, and participate in shaping policies, standards, and decision-making processes related to the Internet’s development and use.
-
E.
IETF participant
An IETF participant is an individual who contributes to the development and review of Internet standards by engaging in IETF working groups, discussions, and document processes.
- 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.