Triple
T9313178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-root |
E224053
|
entity |
| Predicate | operatedBy |
P86
|
FINISHED |
| Object | Verisign |
E37205
|
NE 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: Verisign | Statement: [J-root, operatedBy, Verisign]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Verisign Context triple: [J-root, operatedBy, Verisign]
-
A.
VeriSign
chosen
VeriSign is an American technology company best known for operating key internet infrastructure, including managing the .com and .net top-level domains and providing critical DNS and security services.
-
B.
GoDaddy
GoDaddy is a major American internet domain registrar and web hosting company known for providing online presence and website services to individuals and businesses worldwide.
-
C.
Tucows
Tucows is a Canadian internet services company best known as a major domain name registrar and provider of related web and email services.
-
D.
Akamai Technologies
Akamai Technologies is a leading global content delivery network (CDN) and cloud services provider that optimizes and secures the delivery of online content and applications.
-
E.
Namesys
Namesys was a software company best known for developing the ReiserFS journaling file system for Linux.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c7a0adc4819097ac906f03f0188e |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:37 p.m.