Triple
T15878399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuscarora Nation of New York |
E385009
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sovereign Indigenous community |
C3995
|
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: sovereign Indigenous community Context triple: [Tuscarora Nation of New York, instanceOf, sovereign Indigenous community]
-
A.
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.
-
B.
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.
-
C.
tribal nation
chosen
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
-
D.
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.
-
E.
Nlaka’pamux communities
Nlaka’pamux communities are Indigenous groups in the interior of British Columbia, Canada, who share a common Nlaka’pamux language, culture, and traditional territory along the Fraser and Thompson Rivers, while maintaining distinct local governance and social structures.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:51 a.m.