Triple
T16616695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocom Maya |
E403713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya polity |
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: Maya polity Context triple: [Cocom Maya, instanceOf, Maya polity]
-
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.
Maya royal dynasty
A Maya royal dynasty is a hereditary ruling lineage that governed a Maya city-state, legitimized its authority through divine ancestry, and oversaw political, religious, and military affairs across generations.
-
C.
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.
-
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.
Maya people
The Maya people are an indigenous Mesoamerican civilization known for their advanced writing system, mathematics, astronomy, and monumental architecture, with descendants who continue to maintain rich cultural traditions across present-day Mexico and Central America.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.