Triple
T32518903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICANN Registry Agreement |
E831130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ICANN agreement |
C9664
|
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: ICANN agreement Context triple: [ICANN Registry Agreement, instanceOf, ICANN agreement]
-
A.
ICANN document
chosen
An ICANN document is an official record, policy, report, or communication produced or endorsed by the Internet Corporation for Assigned Names and Numbers concerning the coordination and management of the global domain name system and related internet resources.
-
B.
affiliate of ICANN
An affiliate of ICANN is an organization or entity formally associated with the Internet Corporation for Assigned Names and Numbers to support its mission, programs, or policy development activities without being part of its core governing structure.
-
C.
ICANN structure element
An ICANN structure element is a component within the organizational framework of the Internet Corporation for Assigned Names and Numbers, such as supporting organizations, advisory committees, or stakeholder groups, that participates in the development and implementation of global internet naming and addressing policies.
-
D.
Internet governance community
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.
-
E.
ICANN region
An ICANN region is a geographically defined area used by the Internet Corporation for Assigned Names and Numbers to organize and balance global representation in internet governance and policy-making.
- 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.