Triple
T20537484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbareño/Ventureño Band of Mission Indians |
E504237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chumash tribal community |
C14161
|
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: Chumash tribal community Context triple: [Barbareño/Ventureño Band of Mission Indians, instanceOf, Chumash tribal community]
-
A.
Cocopah community
The Cocopah community is a Native American group centered along the lower Colorado River, maintaining a distinct cultural identity through traditional practices, language, and governance while engaging with surrounding regional societies.
-
B.
Dakelh community
A Dakelh community is a social and territorial group of Dakelh (Carrier) people, rooted in their traditional lands, language, governance, and cultural practices in central British Columbia.
-
C.
Nisenan tribe
The Nisenan tribe is a Native American people indigenous to the California Sierra Nevada foothills and Sacramento Valley, known for their distinct language, cultural traditions, and deep connection to their ancestral lands.
-
D.
Stʼatʼimc community
A Stʼatʼimc community is a group of people belonging to the Stʼatʼimc (Lillooet) Nation, connected by shared territory, language, culture, governance, and kinship within the Interior Plateau region of British Columbia.
-
E.
tribal people
chosen
Tribal people are communities that maintain distinct cultural, social, and often linguistic identities, typically rooted in ancestral lands and traditional ways of life that differ from dominant national societies.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:37 a.m.