Triple
T22566308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADP |
E557960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Human resources services provider |
C40850
|
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: Human resources services provider Context triple: [ADP, instanceOf, Human resources services provider]
-
A.
human resources services provider
chosen
A human resources services provider is an organization that offers specialized support and solutions for managing workforce-related functions such as recruitment, payroll, benefits administration, compliance, and employee development for client businesses.
-
B.
human resources service management solution
A human resources service management solution is a centralized platform that streamlines and automates HR processes, requests, and employee interactions to improve service delivery and workforce experience.
-
C.
payroll service provider
A payroll service provider is a business entity that manages and processes employee compensation, tax withholdings, and related payroll functions on behalf of other organizations.
-
D.
professional services solutions provider
A professional services solutions provider is an organization that delivers specialized expertise, advisory, and implementation services to help clients solve complex business challenges and achieve strategic objectives.
-
E.
human resources department
A human resources department is the organizational unit responsible for managing employee recruitment, development, relations, compensation, and compliance with labor laws and company policies.
- 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_69e11e5ae4ac8190b1f503457603d969 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:52 p.m.