Triple
T1611877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skype for Business Online |
E34631
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud-based communication service |
C6083
|
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: cloud-based communication service Context triple: [Skype for Business Online, instanceOf, cloud-based communication service]
-
A.
instant messaging service
An instant messaging service is a platform that enables users to exchange real-time text, multimedia, and other data over the internet, often supporting presence indicators, group chats, and cross-device synchronization.
-
B.
cloud service
chosen
A cloud service is an on-demand, internet-delivered computing resource—such as storage, processing power, or applications—managed by a provider and accessed remotely by users.
-
C.
omnichannel customer service platform
An omnichannel customer service platform is a unified system that enables businesses to manage and respond to customer interactions seamlessly across multiple channels (such as email, chat, social media, phone, and SMS) from a single interface.
-
D.
video conferencing platform
A video conferencing platform is a digital service that enables real-time audio, video, and content sharing between multiple participants over the internet for meetings, collaboration, and communication.
-
E.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.