Triple
T27440612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achiutla |
E690920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mixtec archaeological site |
C52803
|
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: Mixtec archaeological site Context triple: [Achiutla, instanceOf, Mixtec archaeological site]
-
A.
Zapotec site
A Zapotec site is an archaeological or cultural location associated with the ancient Zapotec civilization, encompassing its settlements, ceremonial centers, and related material remains.
-
B.
San Agustín culture site
A San Agustín culture site is an archaeological location associated with the pre-Columbian San Agustín civilization, characterized by monumental stone sculptures, burial mounds, and ceremonial architecture in the Andean region of Colombia.
-
C.
Mimbres culture site
A Mimbres culture site is an archaeological location associated with the prehistoric Mimbres people of the American Southwest, characterized by pithouses or pueblos, distinctive black-on-white pottery, and evidence of farming-based village life.
-
D.
Olmec site
An Olmec site is an archaeological location associated with the Olmec civilization, characterized by monumental stone sculptures, ceremonial centers, and evidence of early Mesoamerican cultural development.
-
E.
Hohokam archaeological site
A Hohokam archaeological site is a location containing material remains of the Hohokam culture—such as irrigation canals, pit houses, ball courts, artifacts, and ecofacts—that provide evidence of their prehistoric occupation and land use in the American Southwest.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:44 p.m.