Triple
T29794858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gTLDs |
E756517
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | top-level domain category |
C279
|
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: top-level domain category Context triple: [gTLDs, instanceOf, top-level domain category]
-
A.
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).
-
B.
generic top-level domain
chosen
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.
country-code top-level domain policy
A country-code top-level domain policy defines the rules, procedures, and governance structures for the registration, management, and use of internet domains associated with a specific country or territory code (ccTLD).
-
E.
country code top-level domain registry
A country code top-level domain registry is an organization responsible for managing the allocation, administration, and technical operation of internet domain names under a specific country code top-level domain (ccTLD), such as .uk or .jp.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:14 p.m.