Triple
T7558629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .cc |
E178736
|
entity |
| Predicate | registryOperator |
P179
|
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: [.cc, registryOperator, VeriSign]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VeriSign Context triple: [.cc, registryOperator, 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.
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.
-
D.
Comodo Group
Comodo Group is a cybersecurity company best known for its SSL certificates, internet security software, and secure web browser products.
-
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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8dc7d288190a0d08ba704cc3fc2 |
completed | March 27, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c856cc869081909555ae03dec52288 |
completed | March 28, 2026, 10:31 p.m. |
Created at: March 27, 2026, 3:50 p.m.