Triple
T338959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Root Server System Advisory Committee |
E6790
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ICANN advisory committee |
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: ICANN advisory committee Context triple: [Root Server System Advisory Committee, instanceOf, ICANN advisory committee]
-
A.
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.
-
B.
generic top-level domain
A generic top-level domain (gTLD) is a category of top-level domain in the Domain Name System that is not tied to a specific country or territory and is typically used for general or thematic purposes (e.g., .com, .org, .net).
-
C.
sponsored top-level domain
A sponsored top-level domain is an Internet domain extension operated under the guidance of a specific sponsoring organization that represents a defined community and sets eligibility and usage rules for that domain.
-
D.
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.
-
E.
top-level domain
A top-level domain is the last segment of a domain name, appearing after the final dot, that identifies the highest level of the domain name system hierarchy (e.g., .com, .org, .net).
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.