Triple
T35372563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon–British Columbia border |
E1021814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal political border of Canada |
C36444
|
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: internal political border of Canada Context triple: [Yukon–British Columbia border, instanceOf, internal political border of Canada]
-
A.
Canada–Canada internal border
A Canada–Canada internal border is an administrative boundary separating provinces or territories within Canada, delineating their respective jurisdictions while remaining entirely within the sovereign territory of Canada.
-
B.
political border
A political border is an officially recognized dividing line that separates the geographic territories and jurisdictions of different political entities, such as countries, states, or regions.
-
C.
internal border
chosen
An internal border is a boundary within a single country that separates its administrative regions, jurisdictions, or territories without constituting an international frontier.
-
D.
international border
An international border is a legally defined geographic boundary that separates the territories and jurisdictions of two or more sovereign states.
-
E.
territory of Canada
A territory of Canada is a federally governed administrative region with delegated powers from the national government, distinct from provinces which have constitutional authority.
- 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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.