Triple
T33890152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sala silver mine |
E868737
|
entity |
| Predicate | closedAsIndustrialMine |
P130772
|
FINISHED |
| Object | early 20th century |
—
|
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: early 20th century | Statement: [Sala silver mine, closedAsIndustrialMine, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsIndustrialMine Context triple: [Sala silver mine, closedAsIndustrialMine, early 20th century]
-
A.
closedAsCommercialMine
Indicates that a mine ceased operations specifically as a commercial mining enterprise.
-
B.
closedAsIndustrialFacility
chosen
Indicates that an entity ceased operations specifically in its role as an industrial facility.
-
C.
closedAsActiveMine
Indicates that a mine has been officially closed while still being recognized or managed as an active mining site in relevant records or systems.
-
D.
collieryClosed
Indicates that a coal mine (colliery) has ceased operations and is no longer active.
-
E.
closedAsMine
Indicates that an issue or report was closed because it was determined to be a duplicate of one already owned or previously handled by the closer.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 1:48 a.m.