Triple
T17555116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xochicalco archaeological site |
E427571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Columbian Mesoamerican city |
C12166
|
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: pre-Columbian Mesoamerican city Context triple: [Xochicalco archaeological site, instanceOf, pre-Columbian Mesoamerican city]
-
A.
pre-Columbian city
A pre-Columbian city is a large, organized urban settlement in the Americas that existed before European contact, characterized by complex social, political, economic, and religious structures.
-
B.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
-
C.
pre-Columbian site
chosen
A pre-Columbian site is an archaeological location in the Americas that preserves evidence of human activity and cultures that existed before the arrival of Christopher Columbus in 1492.
-
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.
pre-Columbian building
A pre-Columbian building is a structure constructed in the Americas before European contact, reflecting the architectural styles, materials, and cultural practices of indigenous civilizations such as the Maya, Aztec, and Inca.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.