Triple
T1503511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenDNS |
E33848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud-delivered DNS service provider |
C6083
|
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: cloud-delivered DNS service provider Context triple: [OpenDNS, instanceOf, cloud-delivered DNS service provider]
-
A.
cloud service
chosen
A cloud service is an on-demand, internet-delivered computing resource—such as storage, processing power, or applications—managed by a provider and accessed remotely by users.
-
B.
domain name registry
A domain name registry is an authoritative database and management system that stores, maintains, and administers the records of all domain names registered under a specific top-level domain.
-
C.
DNS zone
A DNS zone is an administrative segment of the Domain Name System namespace that contains authoritative DNS records for one or more domains and subdomains managed as a single unit.
-
D.
public domain database
A public domain database is a structured collection of data whose contents are free from intellectual property restrictions, allowing anyone to use, modify, and distribute the data without permission or payment.
-
E.
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.
- 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_69a885f352a4819099b24ff15489dede |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:24 p.m.