Triple
T10880153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snaketown |
E256899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hohokam archaeological site |
C28939
|
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: Hohokam archaeological site Context triple: [Snaketown, instanceOf, Hohokam archaeological site]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
Wari archaeological site
The Wari archaeological site is the remains of an ancient Andean urban and ceremonial center associated with the Wari civilization, featuring complex architecture, administrative compounds, and evidence of early imperial organization in pre-Inca Peru.
-
E.
Wari site
A Wari site is an archaeological location associated with the Wari (Huari) civilization of the central Andes, characterized by planned urban centers, administrative compounds, and distinctive architectural and material culture remains dating roughly from 600–1000 CE.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.