Triple
T36099247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sparwood, British Columbia |
E1044153
|
entity |
| Predicate | hasNearbyCoalMines |
P120102
|
FINISHED |
| Object | Elkview mine |
—
|
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: Elkview mine | Statement: [Sparwood, British Columbia, hasNearbyCoalMines, Elkview mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCoalMines Context triple: [Sparwood, British Columbia, hasNearbyCoalMines, Elkview mine]
-
A.
hasCoalMineNearby
chosen
Indicates that a location or entity is situated close to at least one coal mine.
-
B.
hasNearbyMine
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
C.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
D.
hasNearbyOilField
Indicates that an entity is located close to or in the vicinity of an oil field.
-
E.
isInCoalRegion
Indicates that an entity is located within a geographic region characterized by coal deposits, coal mining, or coal-related activities.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: May 3, 2026, 4:08 p.m.