Triple
T28013294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendat communities in Quebec |
E707477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indigenous community collective |
C12907
|
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: Indigenous community collective Context triple: [Wendat communities in Quebec, instanceOf, Indigenous community collective]
-
A.
indigenous community
chosen
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 clan
An Indigenous clan is a kinship-based social group within an Indigenous community, typically tracing descent from a common ancestor and sharing cultural, spiritual, and territorial responsibilities.
-
C.
Inuit community
An Inuit community is a group of Indigenous Arctic peoples who share close-knit social ties, traditional subsistence practices, and cultural heritage adapted to life in polar environments.
-
D.
Lumad group
A Lumad group is an indigenous community in Mindanao, Philippines, sharing a distinct ethnolinguistic identity, ancestral territory, and traditional socio-cultural practices separate from the region’s dominant Christian and Muslim populations.
-
E.
First Nations community type
A First Nations community type is a classification of Indigenous communities in Canada based on shared cultural, linguistic, historical, and governance characteristics that distinguish them from other First Nations and non-Indigenous populations.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:05 p.m.