Triple
T34837429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | archaeological zone of Tlatelolco |
E1004238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexica archaeological site |
C62113
|
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: Mexica archaeological site Context triple: [archaeological zone of Tlatelolco, instanceOf, Mexica archaeological site]
-
A.
Mixtec archaeological site
A Mixtec archaeological site is a location containing material remains, architecture, and artifacts associated with the pre-Columbian Mixtec civilization, offering evidence of their social, political, religious, and economic 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.
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.
-
E.
Toltec temple
A Toltec temple is a ceremonial structure built by the Toltec civilization, serving as a religious, political, and cultural center often characterized by pyramidal platforms, columned halls, and sculpted warrior figures.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.