Triple
T32517351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .com |
E831092
|
entity |
| Predicate | dnsSponsoringOrganization |
P59447
|
FINISHED |
| Object | Verisign |
—
|
NE NERFINISHED |
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: [.com, dnsSponsoringOrganization, Verisign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dnsSponsoringOrganization Context triple: [.com, dnsSponsoringOrganization, Verisign]
-
A.
sponsoringAgency
chosen
Indicates that one entity serves as the sponsoring agency that provides support, backing, or authorization for another entity or activity.
-
B.
connectedOrganization
Indicates that there is an established relationship or association between two organizations, such that one is linked or affiliated with the other in some relevant context.
-
C.
endedOrganization
Indicates that an organization has ceased to exist or operate, marking the termination of its existence or activities.
-
D.
organizationName
Indicates that an entity has a specific official name as an organization.
-
E.
sponsoringOrganizationType
Indicates the kind or category of organization that provides sponsorship or support in the described relationship or activity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4aabff08190ad437b687dd41f8d |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.