Triple
T19209296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Automatic Data Processing |
E480315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human resources services company |
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 company Context triple: [Automatic Data Processing, instanceOf, human resources services company]
-
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.
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.
-
D.
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.
-
E.
recruitment agency
A recruitment agency is an organization that connects employers with suitable job candidates by sourcing, screening, and recommending talent for open positions.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:20 p.m.