Triple
T31790462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmberget |
E811448
|
entity |
| Predicate | hasConsequenceOfMining |
P204081
|
FINISHED |
| Object | relocation of residents |
—
|
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: relocation of residents | Statement: [Malmberget, hasConsequenceOfMining, relocation of residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsequenceOfMining Context triple: [Malmberget, hasConsequenceOfMining, relocation of residents]
-
A.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
B.
eraOfMajorMiningActivity
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.
hasConsequenceHypothesis
Indicates that one situation, event, or statement is hypothesized to lead to or imply a particular consequence.
-
E.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a031b40c6d0819096f4b9787a1f09d1 |
completed | May 12, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_6a03191f8ee08190b3416b044869ddfd |
completed | May 12, 2026, 12:12 p.m. |
| PDg | Predicate description generation | batch_6a031b401e7c8190b9d413e2bc3d3fec |
completed | May 12, 2026, 12:21 p.m. |
Created at: April 30, 2026, 11:39 p.m.