Triple
T19298960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coatlan |
E482642
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesoamerican city-state |
C6681
|
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-state Context triple: [Coatlan, instanceOf, Mesoamerican city-state]
-
A.
pre-Columbian city-state
chosen
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.
-
B.
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.
-
C.
pre-Columbian Mesoamerican institution
A pre-Columbian Mesoamerican institution is an organized social, political, religious, or economic structure—such as a temple complex, marketplace, or governing council—that regulated and shaped communal life in Mesoamerican societies before European contact.
-
D.
Mesoamerican alliance
A Mesoamerican alliance is a political and military coalition formed between pre-Columbian Mesoamerican city-states or polities to coordinate warfare, trade, tribute, and regional dominance.
-
E.
Inca polity
The Inca polity was a highly centralized, hierarchical imperial state in the Andes that integrated diverse ethnic groups through a complex system of administration, tribute, and state-sponsored religion centered on the Sapa 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:31 p.m.