Triple
T7857944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamics 365 Field Service |
E182423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cloud-based business 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: cloud-based business application Context triple: [Dynamics 365 Field Service, instanceOf, cloud-based business application]
-
A.
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.
-
B.
cloud service
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.
cloud computing platform
A cloud computing platform is an integrated environment that provides on-demand access to scalable computing resources, storage, and services over the internet, enabling users to deploy, manage, and run applications without managing underlying hardware.
-
D.
cloud services company
A cloud services company provides on-demand computing resources, storage, and software platforms over the internet, enabling organizations to scale and manage their IT infrastructure efficiently without owning physical hardware.
-
E.
application service organization
An application service organization is a business entity that delivers software applications and related IT services to clients, typically over a network, managing deployment, maintenance, and support on their behalf.
- 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.