Triple
T11203909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Factory Act 1833 |
E265108
|
entity |
| Predicate | limitedWorkingHoursOf |
P69039
|
FINISHED |
| Object | 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: children aged 9 to 13 | Statement: [Factory Act 1833, limitedWorkingHoursOf, children aged 9 to 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedWorkingHoursOf Context triple: [Factory Act 1833, limitedWorkingHoursOf, 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.
hoursOfOperation
Indicates the time periods during which a place or service is open and available for use.
-
C.
usedInBusinessHours
Indicates that something is utilized or occurs during designated business operating hours.
-
D.
hasLimitedWeekdayService
Indicates that the service operates on weekdays only during restricted or reduced hours or on a limited schedule.
-
E.
daysOfOperation
Indicates the specific days on which an entity (such as a service, facility, or operation) is active or functioning.
- 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.