Triple
T2606028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carer’s Allowance |
E58659
|
entity |
| Predicate | requiresCareHoursPerWeek |
P3841
|
FINISHED |
| Object | at least 35 hours |
—
|
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: at least 35 hours | Statement: [Carer’s Allowance, requiresCareHoursPerWeek, at least 35 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCareHoursPerWeek Context triple: [Carer’s Allowance, requiresCareHoursPerWeek, at least 35 hours]
-
A.
requiresCare
Indicates that one entity depends on another to provide care, attention, or maintenance for its proper functioning or well-being.
-
B.
workLengthRequirement
chosen
Indicates that there is a specified minimum or exact duration of work required for something (e.g., a job, task, or role).
-
C.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
D.
requiredOccupationOf
Indicates that one entity specifies the occupation or job role that is required or expected for another entity (such as a position, task, or qualification).
-
E.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.