Triple
T9282002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .xk |
E223090
|
entity |
| Predicate | hasTopLevelDomainFormat |
P52129
|
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: [.xk, hasTopLevelDomainFormat, ccTLD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopLevelDomainFormat Context triple: [.xk, hasTopLevelDomainFormat, ccTLD]
-
A.
hasTopLevelDomain
chosen
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).
-
B.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
C.
hasLegalDomain
Indicates that a legal rule, right, obligation, or concept applies within a specific jurisdiction, legal system, or domain of law.
-
D.
hasSubdomain
Indicates that one domain is a subordinate or nested part of another domain within a hierarchical naming structure.
-
E.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081c2b048190aa6930de3bf2f87f |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.