Triple
T24871817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson-Huron Treaty area |
E622453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic treaty territory |
C47402
|
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: historic treaty territory Context triple: [Robinson-Huron Treaty area, instanceOf, historic treaty territory]
-
A.
treaty area
chosen
A treaty area is a geographically defined region whose governance, resource use, or legal status is regulated by one or more formal agreements between sovereign entities or authorities.
-
B.
modern treaty
A modern treaty is a contemporary, negotiated agreement between Indigenous peoples and a state that defines rights, land ownership, governance, and resource management in a legally binding framework.
-
C.
historic state
A historic state is a former political entity or government that once exercised sovereignty over a defined territory and population but has since ceased to exist in its original form.
-
D.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
E.
indigenous territory
An indigenous territory is a geographically defined area traditionally inhabited, used, or managed by an Indigenous people, where they maintain cultural, spiritual, social, and often legal relationships to the land and its resources.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:23 a.m.