Triple
T34784632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KN |
E1002770
|
entity |
| Predicate | relatedCcTLD |
—
|
GENERATED |
| Object | .kn |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCcTLD Context triple: [KN, relatedCcTLD, .kn]
-
A.
relatedTLD
chosen
Indicates that one top-level domain (TLD) has an association or connection with another TLD, such as similarity, shared purpose, or contextual relevance.
-
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.
connectedDomain
Indicates that one domain is linked or associated with another domain in a meaningful or functional way.
-
E.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.