Triple
T25064329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorkForce West Virginia |
E627741
|
entity |
| Predicate | employerService |
P158397
|
FINISHED |
| Object | recruitment assistance |
—
|
LITERAL 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: recruitment assistance | Statement: [WorkForce West Virginia, employerService, recruitment assistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerService Context triple: [WorkForce West Virginia, employerService, recruitment assistance]
-
A.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
B.
employerSide
Indicates that the subject participates in or represents the employer’s position, interests, or perspective within an employment relationship or dispute.
-
C.
employerRight
Indicates that an employer holds a specific right, entitlement, or legal authority in relation to an employee or employment situation.
-
D.
employer
Indicates a relationship where one entity hires, pays, and oversees the work of another entity.
-
E.
employerOrPartner
Indicates that one entity is either the employer of, or a business partner with, another entity.
- F. None of above. chosen
Provenance (4 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46d3f35848190b56a4373c97a7d64 |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 18, 2026, 6:10 a.m.