Triple
T9932927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Registries Stakeholder Group |
E192688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ICANN GNSO stakeholder group |
C9558
|
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 GNSO stakeholder group Context triple: [Registries Stakeholder Group, instanceOf, ICANN GNSO stakeholder group]
-
A.
ICANN document
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
chosen
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.
IETF working group
An IETF working group is a collaborative, time-bounded team of experts chartered within the Internet Engineering Task Force to develop, discuss, and standardize specific Internet technologies or protocols.
-
E.
IETF area
An IETF area is a high-level organizational division within the Internet Engineering Task Force that groups related working groups and activities under a common technical or functional theme.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:44 p.m.