Triple
T6471568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Albany First Nation |
E142364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | First Nations band government |
C16745
|
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: First Nations band government Context triple: [Fort Albany First Nation, instanceOf, First Nations band government]
-
A.
tribal nation
A tribal nation is a sovereign Indigenous community recognized as a distinct political and cultural entity with its own government, territory, and traditions.
-
B.
Indian band government
chosen
An Indian band government is the local governing authority of a First Nations band in Canada, responsible for administering band affairs, managing community services and resources, and representing its members in dealings with other governments.
-
C.
federally recognized tribe
A federally recognized tribe is a Native American or Alaska Native governing body that the U.S. federal government formally acknowledges as a sovereign political entity with a government-to-government relationship and eligibility for specific legal rights, services, and protections.
-
D.
Aboriginal land council
An Aboriginal land council is a representative body established to advocate for, manage, and protect the land rights, cultural heritage, and interests of Aboriginal communities within a defined region.
-
E.
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.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:50 p.m.