Triple
T7790684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skype for Business Web App |
E187369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Skype for Business client |
C12359
|
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: Skype for Business client Context triple: [Skype for Business Web App, instanceOf, Skype for Business client]
-
A.
Skype service feature
A Skype service feature is a distinct capability or tool within the Skype platform that enables users to communicate, collaborate, or manage their interactions through functions such as voice and video calls, messaging, file sharing, and screen sharing.
-
B.
VoIP client
chosen
A VoIP client is an application or device that enables users to make and receive voice (and often video) calls over IP networks instead of traditional telephone lines.
-
C.
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.
-
D.
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.
-
E.
Windows app platform
A Windows app platform is a comprehensive framework and runtime environment that provides the tools, APIs, and services needed to build, deploy, and run applications on Windows devices.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 4:25 p.m.