Triple
T10721817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Buck |
E252839
|
entity |
| Predicate | employmentStatusAtStart |
P72402
|
FINISHED |
| Object | dishwasher |
—
|
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: dishwasher | Statement: [Joe Buck, employmentStatusAtStart, dishwasher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employmentStatusAtStart Context triple: [Joe Buck, employmentStatusAtStart, dishwasher]
-
A.
isUnemployedAtStartOf
Indicates that an individual is unemployed at the beginning of a specified time period or event.
-
B.
stateOfEmployment
chosen
Indicates that one entity’s employment status or condition is defined in relation to another entity (such as an employer, position, or employment situation).
-
C.
careerStatus
Indicates the current stage, position, or condition of an entity within its professional or occupational life.
-
D.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
-
E.
employedTo
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d43655081909b071100c96cb4f6 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:13 p.m.