Triple
T22353627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Split Lake, Manitoba |
E552595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | settlement in Manitoba |
C46148
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: settlement in Manitoba Context triple: [Split Lake, Manitoba, instanceOf, settlement in Manitoba]
-
A.
settlement in British Columbia
A settlement in British Columbia is a populated place—such as a city, town, village, or unincorporated community—located within the provincial boundaries of British Columbia, Canada.
-
B.
settlement in Nunavut
A settlement in Nunavut is a small, often remote community within Canada's northern territory, typically characterized by predominantly Inuit populations, limited infrastructure, and reliance on local resources and traditional lifestyles.
-
C.
Manitoba legislation
Manitoba legislation is the body of laws and statutes enacted by the Legislative Assembly of Manitoba that govern the rights, responsibilities, and conduct of individuals, organizations, and government within the province.
-
D.
road in Manitoba
A road in Manitoba is a designated transportation route within the Canadian province of Manitoba, facilitating vehicular travel and connectivity between communities, regions, and key destinations.
-
E.
subregion of Saskatchewan
A subregion of Saskatchewan is a defined geographic area within the province characterized by shared physical, economic, cultural, or administrative features that distinguish it from other parts of Saskatchewan.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:44 p.m.