Triple
T4576516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .台湾 |
E123151
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internationalized country-code top-level domain |
C653
|
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: internationalized country-code top-level domain Context triple: [.台湾, instanceOf, internationalized country-code top-level domain]
-
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.
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.
-
C.
country code top-level domain
chosen
A country code top-level domain is a two-letter Internet domain suffix assigned to a specific country or territory, used to indicate geographic association in web addresses.
-
D.
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).
-
E.
ccTLD operators community
The ccTLD operators community is a collaborative group of organizations and professionals responsible for managing and coordinating country-code top-level domains, sharing best practices, policies, and technical expertise to support a stable and secure global domain name system.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 1:10 p.m.