Triple
T27105590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowell system of industrial organization |
E686567
|
entity |
| Predicate | workingDaysPerWeek |
P6441
|
FINISHED |
| Object | six‑day workweek |
—
|
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: six‑day workweek | Statement: [Lowell system of industrial organization, workingDaysPerWeek, six‑day workweek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingDaysPerWeek Context triple: [Lowell system of industrial organization, workingDaysPerWeek, six‑day workweek]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
workweekAssociation
Indicates an association between entities based on their connection to a specific workweek or workweek schedule.
-
C.
timePeriodOfWorks
Indicates the span of time during which the associated works were created, produced, or active.
-
D.
workPattern
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
E.
hasWeekLength
chosen
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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623fcc6c881908e76b65c0ee51dd4 |
completed | May 2, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:50 a.m.