Triple
T28721513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooks Hatlen |
E730105
|
entity |
| Predicate | worksAsAfterParole |
P81883
|
FINISHED |
| Object | grocery store bagger |
—
|
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: grocery store bagger | Statement: [Brooks Hatlen, worksAsAfterParole, grocery store bagger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAsAfterParole Context triple: [Brooks Hatlen, worksAsAfterParole, grocery store bagger]
-
A.
restrictionAfterPardon
Indicates that a restriction or limitation is imposed on an entity following the granting of a pardon.
-
B.
eventuallyParoled
chosen
Indicates that an individual who was previously incarcerated was later released from prison on parole.
-
C.
paroleEligibility
Indicates whether and under what conditions an individual is legally eligible to be considered for release on parole.
-
D.
isForConvictedOffenders
Indicates that something is intended to apply to, be used by, or be relevant for individuals who have been legally convicted of offenses.
-
E.
workPermitted
Indicates that one entity is allowed or authorized to perform work or employment-related activities in relation to another entity or within a given context.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 5:53 a.m.