Triple
T4001021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taos Pueblo |
E89413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Pueblo community |
C13971
|
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: Pueblo community Context triple: [Taos Pueblo, instanceOf, Pueblo community]
-
A.
Puebloan people
chosen
The Puebloan people are Native American communities of the Southwestern United States known for their long-standing traditions of settled village life, intricate adobe and stone architecture, and rich cultural, artistic, and agricultural practices.
-
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.
Indian reservation
An Indian reservation is a tract of land managed by a Native American tribe under the U.S. Bureau of Indian Affairs, where the tribe exercises certain sovereign rights and self-governance.
-
D.
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.
-
E.
Southern Paiute people
The Southern Paiute people are a Native American group indigenous to the Great Basin and Colorado Plateau regions of the southwestern United States, known for their rich cultural traditions, close relationship with the land, and resilience in the face of colonization and displacement.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.