Triple
T5890946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebel.com |
E130985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | domain name registrar |
C19486
|
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: domain name registrar Context triple: [Rebel.com, instanceOf, domain name registrar]
-
A.
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.
-
B.
domain name registry operator
A domain name registry operator is an organization responsible for managing the database of all domain names under a specific top-level domain, including their registration, renewal, and technical DNS infrastructure.
-
C.
domain
A domain is a specific area of knowledge, activity, or interest that defines the scope and boundaries within which concepts, rules, and relationships are organized and understood.
-
D.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
E.
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).
- F. None of above. chosen
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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.