Triple
T14285969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teotihuacan archaeological zone (partly within state jurisdiction) |
E354176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesoamerican city |
C11539
|
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: Mesoamerican city Context triple: [Teotihuacan archaeological zone (partly within state jurisdiction), instanceOf, Mesoamerican city]
-
A.
pre-Columbian city
chosen
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.
Aztec mythological location
An Aztec mythological location is a sacred or supernatural place within Aztec cosmology, such as realms of gods, the afterlife, or cosmic landmarks, that structures religious belief, ritual, and narrative.
-
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.
Maya city
A Maya city is a pre-Columbian urban center of the Maya civilization characterized by monumental architecture, complex social and political organization, and integration with surrounding agricultural and ritual landscapes.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:11 a.m.