Triple
T27302134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bathurst District |
E688940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Upper Canada |
C36594
|
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: district of Upper Canada Context triple: [Bathurst District, instanceOf, district of Upper Canada]
-
A.
institution of Upper Canada
An institution of Upper Canada is an organized body, such as a governmental, legal, educational, or religious organization, established in the historical British colony of Upper Canada to administer public affairs, provide services, or uphold social order.
-
B.
former subdivision of Upper Canada
chosen
A former subdivision of Upper Canada is an obsolete administrative district or county that once formed part of the colonial province’s territorial organization before later reforms or Confederation altered its boundaries or status.
-
C.
subregion of Ontario
A subregion of Ontario is a defined geographic area within the province characterized by shared administrative, economic, cultural, or environmental features that distinguish it from other parts of Ontario.
-
D.
province of British North America
A province of British North America was a colonial administrative division under British rule in North America prior to Canadian Confederation, encompassing territories such as Upper Canada, Lower Canada, Nova Scotia, and others.
-
E.
province of Canada
A province of Canada is a primary administrative division of the country with its own government, legislature, and constitutional powers distinct from the federal government.
- F. None of above.
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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:22 a.m.