Triple
T7857945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamics 365 Field Service |
E182423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Microsoft Dynamics 365 application |
C17175
|
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: Microsoft Dynamics 365 application Context triple: [Dynamics 365 Field Service, instanceOf, Microsoft Dynamics 365 application]
-
A.
Salesforce product
A Salesforce product is a configurable item or service offered by a business that can be sold, priced, and tracked within the Salesforce platform for quoting, ordering, and revenue management.
-
B.
enterprise software-as-a-service platform
chosen
An enterprise software-as-a-service platform is a cloud-based solution that delivers scalable, secure, and centrally managed business applications to organizations on a subscription basis.
-
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.
enterprise portal software
Enterprise portal software is a centralized, web-based platform that integrates applications, data, and services to provide personalized, secure access and collaboration tools for employees, partners, and customers across an organization.
-
E.
Lisa application
The Lisa application is a software program designed to run on the Lisa operating environment, providing users with specific productivity or utility functions through a graphical user interface.
- 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:52 p.m.