Triple
T18003488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker Lake |
E430684
|
entity |
| Predicate | nearbyResourceDevelopment |
P79682
|
FINISHED |
| Object | mining projects in Kivalliq Region |
—
|
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: mining projects in Kivalliq Region | Statement: [Baker Lake, nearbyResourceDevelopment, mining projects in Kivalliq Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyResourceDevelopment Context triple: [Baker Lake, nearbyResourceDevelopment, mining projects in Kivalliq Region]
-
A.
nearbyResourcePotential
Indicates that a resource is likely available or exploitable in the vicinity of the referenced entity or location.
-
B.
hasNearbyDevelopment
chosen
Indicates that a development or construction project exists in close physical proximity to the referenced entity.
-
C.
nearbyProject
Indicates that one entity is located close to or in the immediate vicinity of another entity or project.
-
D.
nearbyEconomicActivity
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
-
E.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b3ea60608190b977644e946407b7 |
completed | April 19, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.