Triple
T6497018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca forces |
E148783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armed forces of a pre-Columbian empire |
C2458
|
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: armed forces of a pre-Columbian empire Context triple: [Inca forces, instanceOf, armed forces of a pre-Columbian empire]
-
A.
Aztec military order
An Aztec military order was an elite, hierarchically organized warrior society within the Aztec Empire, whose members earned status and privileges through battlefield achievements and played key roles in warfare, politics, and religious ceremonies.
-
B.
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.
-
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.
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.
-
E.
historical armed forces
chosen
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:41 p.m.