Triple
T9767727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .net |
E237037
|
entity |
| Predicate | hasWhoisService |
P35464
|
FINISHED |
| Object | whois.verisign-grs.com |
—
|
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: whois.verisign-grs.com | Statement: [.net, hasWhoisService, whois.verisign-grs.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWhoisService Context triple: [.net, hasWhoisService, whois.verisign-grs.com]
-
A.
whoisServer
chosen
Indicates that one entity functions as the WHOIS server responsible for providing registration and ownership information about another entity (typically a domain or IP resource).
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
D.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for another entity.
-
E.
hasServiceChief
Indicates that one entity serves as the chief or head responsible for overseeing the services of 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0a2da648190836916a45d2998d7 |
completed | April 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.