Triple
T35466333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONADI |
E1025083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Corporation for Indigenous Development |
C65931
|
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: National Corporation for Indigenous Development Context triple: [CONADI, instanceOf, National Corporation for Indigenous Development]
-
A.
First Nations tribal council
A First Nations tribal council is a governing body composed of representatives from one or more Indigenous communities that makes collective decisions on political, social, economic, and cultural matters affecting their people.
-
B.
Inuvialuit organization
An Inuvialuit organization is a formal entity established by or for Inuvialuit people to represent their interests, manage land and resource rights, deliver programs and services, and promote cultural, social, and economic well-being within the Inuvialuit Settlement Region and beyond.
-
C.
Nlaka'pamux band government
The Nlaka'pamux band government is the local Indigenous governing body responsible for administering the affairs, lands, programs, and services of a specific Nlaka'pamux First Nation community.
-
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.
Indigenous elders council
A group of respected senior members of an Indigenous community who provide cultural guidance, wisdom, and leadership in decision-making and governance.
- F. None of above. chosen
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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.