Triple
T7857943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamics 365 Field Service |
E182423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | field service management software |
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: field service management software Context triple: [Dynamics 365 Field Service, instanceOf, field service management software]
-
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.
facility management company
A facility management company is an organization that plans, operates, and maintains buildings and their services to ensure safe, efficient, and cost-effective environments for occupants and owners.
-
C.
task management service
A task management service is a system that allows users to create, organize, prioritize, track, and complete tasks or projects, often collaboratively and across multiple devices.
-
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.
home services platform
A home services platform is a digital marketplace that connects homeowners with vetted local professionals for tasks such as cleaning, repairs, maintenance, and renovations, enabling easy booking, payment, and service management.
- 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.