Triple
T7755918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lowell mill girls |
E175894
|
entity |
| Predicate | workingConditions |
P39555
|
FINISHED |
| Object | crowded mills |
—
|
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: crowded mills | Statement: [Lowell mill girls, workingConditions, crowded mills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingConditions Context triple: [Lowell mill girls, workingConditions, crowded mills]
-
A.
workConditions
chosen
Indicates the terms, environment, and circumstances under which work or a job is performed.
-
B.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
-
C.
workPermitted
Indicates that one entity is allowed or authorized to perform work or employment-related activities in relation to another entity or within a given context.
-
D.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
E.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.