Triple
T6732501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocumtuck homeland |
E153668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traditional Indigenous territory |
C7845
|
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: traditional Indigenous territory Context triple: [Pocumtuck homeland, instanceOf, traditional Indigenous territory]
-
A.
traditional homeland
chosen
A traditional homeland is a geographic area historically inhabited, used, and culturally identified with by an Indigenous or long-established community, forming the core of its ancestral identity and way of life.
-
B.
First Nations reserve
A First Nations reserve is a tract of land set aside under the Indian Act and treaty agreements for the use and benefit of a specific First Nations community, typically governed by that community’s band council.
-
C.
indigenous community
An indigenous community is a group of people with historical continuity to pre-colonial or original inhabitants of a region, maintaining distinct cultural, social, and political traditions tied to their ancestral lands and identities.
-
D.
indigenous comarca
An indigenous comarca is a legally recognized territorial and administrative region governed by indigenous peoples, where they exercise cultural, political, and land rights according to their traditions and national law.
-
E.
Indian reserve
An Indian reserve is a tract of land set aside under federal authority for the use and benefit of a specific First Nations community, typically governed by band leadership and subject to distinct legal and administrative frameworks.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:09 p.m.