Triple
T11203912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Factory Act 1833 |
E265108
|
entity |
| Predicate | maximumHoursPerWeekFor |
P69039
|
FINISHED |
| Object | 48 hours for children aged 9 to 13 |
—
|
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: 48 hours for children aged 9 to 13 | Statement: [Factory Act 1833, maximumHoursPerWeekFor, 48 hours for children aged 9 to 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumHoursPerWeekFor Context triple: [Factory Act 1833, maximumHoursPerWeekFor, 48 hours for children aged 9 to 13]
-
A.
workHoursLimit
chosen
Indicates a constraint on the maximum number of hours an entity is allowed or scheduled to work within a specified period.
-
B.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
-
C.
workLengthRequirement
Indicates that there is a specified minimum or exact duration of work required for something (e.g., a job, task, or role).
-
D.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
E.
hasWeekLength
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.