Triple
T6972876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appirio |
E161638
|
entity |
| Predicate | usesPlatform |
P1292
|
FINISHED |
| Object | Workday |
E387789
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Workday | Statement: [Appirio, usesPlatform, Workday]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Workday Context triple: [Appirio, usesPlatform, Workday]
-
A.
Workday
chosen
Workday is a cloud-based enterprise software company best known for its human capital management and financial management applications used by large organizations worldwide.
-
B.
Paylocity
Paylocity is a U.S.-based provider of cloud payroll and human capital management software solutions for businesses.
-
C.
ADP
ADP is a leading global provider of payroll, human capital management, and HR outsourcing solutions for businesses of all sizes.
-
D.
Paycom
Paycom is a U.S.-based software company that provides cloud-based payroll and human capital management solutions to businesses.
-
E.
PeopleSoft
PeopleSoft is an enterprise software company best known for its human resources and financial management applications, later integrated into Oracle’s product portfolio.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db3aad108190b19df2d21f5ce168 |
completed | March 27, 2026, 7:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761a2b2f481908718b4803cfbfae9 |
completed | March 28, 2026, 5:05 a.m. |
Created at: March 27, 2026, 2:30 p.m.