Triple
T22059286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Collections and Digital Services |
E545108
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital services unit |
C32089
|
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: digital services unit Context triple: [Special Collections and Digital Services, instanceOf, digital services unit]
-
A.
digital services organization
chosen
A digital services organization is an entity that designs, builds, and operates technology-enabled solutions—such as software platforms, applications, and online services—to deliver value and outcomes for customers and stakeholders.
-
B.
digital platform
A digital platform is an online infrastructure that facilitates interactions, transactions, or value exchange between users, services, or systems through integrated digital tools and interfaces.
-
C.
digital wallet service
A digital wallet service is an online platform or application that securely stores users’ payment information and enables them to make electronic transactions, manage funds, and access financial services via digital devices.
-
D.
universal service support mechanism
A universal service support mechanism is a regulatory and financial framework designed to ensure that essential communication services are available, affordable, and accessible to all users, including those in high-cost or underserved areas.
-
E.
cloud computing company unit
A cloud computing company unit is an organizational division that designs, delivers, and manages cloud-based infrastructure, platforms, or software services for internal or external customers.
- F. None of above.
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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:27 p.m.