Triple
T20735711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Frazee |
E509697
|
entity |
| Predicate | refusedEmploymentBecause |
P37898
|
FINISHED |
| Object | offered job required Sunday work |
—
|
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: offered job required Sunday work | Statement: [William Frazee, refusedEmploymentBecause, offered job required Sunday work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedEmploymentBecause Context triple: [William Frazee, refusedEmploymentBecause, offered job required Sunday work]
-
A.
rejectedBecause
chosen
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
B.
refusedDuty
Indicates that an entity declined or failed to accept or perform a duty, task, or responsibility that was expected or assigned.
-
C.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
eligibleWork
Indicates that a particular work satisfies the necessary conditions or criteria to qualify for a specified status, benefit, or consideration.
-
E.
rejectedRequirement
Indicates that a proposed requirement has been evaluated and explicitly not accepted or approved.
- F. None of above.
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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20a02d48190bba22d1bdbeb370d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:31 p.m.