Triple
T869270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec Empire |
E18773
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pre-Columbian state |
C397
|
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 state Context triple: [Aztec Empire, instanceOf, pre-Columbian state]
-
A.
ancient kingdom
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
-
B.
former sovereign state
chosen
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
-
C.
Andean culture
Andean culture encompasses the diverse traditions, social structures, and belief systems developed by indigenous peoples of the Andes, characterized by highland agriculture, intricate textiles, communal organization, and deep spiritual ties to the mountainous landscape.
-
D.
vassal state
A vassal state is a subordinate political entity that retains limited internal autonomy while owing allegiance, tribute, or military support to a more powerful sovereign state.
-
E.
early modern state
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.