Triple
T22388701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willie Horton |
E553460
|
entity |
| Predicate | furloughType |
P74490
|
FINISHED |
| Object | weekend furlough |
—
|
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: weekend furlough | Statement: [Willie Horton, furloughType, weekend furlough]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furloughType Context triple: [Willie Horton, furloughType, weekend furlough]
-
A.
flexibleFurloughIntroducedOn
Indicates the date on which a flexible furlough arrangement was first implemented or came into effect.
-
B.
leaveType
chosen
Indicates the type or category of leave associated with an absence or time-off event (e.g., vacation, sick leave, parental leave).
-
C.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
D.
filingTypeCode
Indicates the specific category or type of filing associated with a submitted document or record.
-
E.
representedEmployeeType
Indicates that one entity serves as a representative or exemplar of a particular type or category of employee 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15858c13c819098fe66a50ecea7d7 |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.