Triple
T33299694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eveleth Taconite Company |
E852544
|
entity |
| Predicate | hasWorkplaceIssue |
P195700
|
FINISHED |
| Object | sexual harassment |
—
|
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: sexual harassment | Statement: [Eveleth Taconite Company, hasWorkplaceIssue, sexual harassment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkplaceIssue Context triple: [Eveleth Taconite Company, hasWorkplaceIssue, sexual harassment]
-
A.
associatedWithWorkplace
Indicates a relationship where an entity has a connection or affiliation with a particular workplace or place of employment.
-
B.
postOccupationIssue
Indicates that an issue or problem arises or is identified after an occupation, role, or position has ended.
-
C.
hasOccupationInWork
Indicates that an entity holds or performs a specific occupation within a particular work, project, or creative production.
-
D.
hasNotableConnectionToWork
Indicates that there is a significant or noteworthy relationship, influence, or association between an entity and a particular work.
-
E.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: May 1, 2026, 1:33 a.m.