Triple
T23342387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auburn system |
E591768
|
entity |
| Predicate | workRegime |
P3027
|
FINISHED |
| Object | group labor in workshops |
—
|
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: group labor in workshops | Statement: [Auburn system, workRegime, group labor in workshops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workRegime Context triple: [Auburn system, workRegime, group labor in workshops]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
workPattern
Indicates the typical schedule, structure, or arrangement according to which an entity performs its work or duties.
-
C.
laborSystem
chosen
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
-
D.
workMode
Indicates the manner, configuration, or operational state in which an entity performs its work or function.
-
E.
workweekAssociation
Indicates an association between entities based on their connection to a specific workweek or workweek schedule.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198334dec819081c432b434eb3ba5 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.