Triple
T10862472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .sx |
E256438
|
entity |
| Predicate | TLDClass |
P19623
|
FINISHED |
| Object | ccTLD |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ccTLD | Statement: [.sx, TLDClass, ccTLD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TLDClass Context triple: [.sx, TLDClass, ccTLD]
-
A.
TLDType
chosen
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
B.
ccTLDManager
Indicates that an entity is responsible for administering and managing a specific country-code top-level domain (ccTLD) on behalf of a country or territory.
-
C.
internetTLD
Indicates that one entity is the internet top-level domain (TLD) associated with the other entity.
-
D.
hasTopLevelDomain
Indicates that one entity (typically a website, domain name, or internet resource) is associated with a specific top-level domain (such as .com, .org, or .uk).
-
E.
managesTopLevelDomain
Indicates that one entity has administrative authority over and is responsible for operating and maintaining a specific top-level domain on the internet.
- F. None of above.
Provenance (3 batches)
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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7515238108190a72eb8cd147f223d |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.