Triple
T34472479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keweenaw copper mining district |
E884941
|
entity |
| Predicate | lastMajorMinesClosed |
P31791
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Keweenaw copper mining district, lastMajorMinesClosed, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorMinesClosed Context triple: [Keweenaw copper mining district, lastMajorMinesClosed, 1960s]
-
A.
minesOperatedBy
Indicates that a mine is operated or run by a particular organization or entity.
-
B.
eraOfMajorMiningActivity
chosen
Indicates the time period during which significant or primary mining operations took place for the associated entity.
-
C.
wasExtensivelyMinedIn
Indicates that a location or resource was subject to intensive or large-scale mining activity during a specified time or by a specified agent.
-
D.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
-
E.
miningDisaster
Indicates a disastrous event occurring in the context of mining operations, typically involving significant damage, injury, or loss of life.
- 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_69f349c880408190ade571c471ab154a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7199f91ec8190a4459f389a914cf0 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2:01 a.m.