Triple
T26747203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LKAB |
E674432
|
entity |
| Predicate | mainMiningRegion |
P115090
|
FINISHED |
| Object | Norrbotten County |
—
|
NE NERFINISHED |
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: Norrbotten County | Statement: [LKAB, mainMiningRegion, Norrbotten County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainMiningRegion Context triple: [LKAB, mainMiningRegion, Norrbotten County]
-
A.
isMiningRegion
Indicates that a region is characterized by or designated for mining activities or mineral extraction.
-
B.
connectsToMiningRegion
Indicates a relationship where something is physically or functionally linked to a mining region, such as through infrastructure, operations, or direct access.
-
C.
hasMiningDistrict
Indicates that an entity possesses, contains, or is associated with a designated mining district within its domain or jurisdiction.
-
D.
hasMiningArea
Indicates that an entity possesses, controls, or is associated with a designated area where mining activities take place.
-
E.
locatedInMiningBelt
chosen
Indicates that an entity is situated within a designated mining belt or mining region.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6188630dc8190ba0602ebe2b3ab6b |
completed | May 2, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:52 a.m.