Triple
T2601819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorkuta camps |
E58359
|
entity |
| Predicate | workConditions |
P39555
|
FINISHED |
| Object | long shifts in coal mines |
—
|
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: long shifts in coal mines | Statement: [Vorkuta camps, workConditions, long shifts in coal mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workConditions Context triple: [Vorkuta camps, workConditions, long shifts in coal mines]
-
A.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
-
B.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
E.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
- F. None of above. chosen
Provenance (4 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd459ca6c81908505be96d097b739 |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1c7b6e48190be9a0c31069df797 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:49 p.m.