Triple
T23331734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Native American forces of Chief Tuskaloosa |
E591461
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mississippian culture military coalition |
C38100
|
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: Mississippian culture military coalition Context triple: [Native American forces of Chief Tuskaloosa, instanceOf, Mississippian culture military coalition]
-
A.
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.
-
B.
military confederacy
chosen
A military confederacy is a loose alliance of semi-independent states or groups that coordinate their armed forces and defense policies for mutual security while retaining significant political autonomy.
-
C.
Mississippian culture center
A Mississippian culture center is a facility or site dedicated to preserving, interpreting, and educating the public about the Mississippian Native American civilization, its mound-building traditions, and its social, political, and religious practices.
-
D.
tribal confederation
A tribal confederation is a loose alliance of distinct tribes that cooperate for mutual defense, governance, or shared interests while retaining their individual identities and autonomy.
-
E.
Pueblo ceremonial organization
A Pueblo ceremonial organization is a structured religious and social institution within Pueblo communities that coordinates rituals, dances, and sacred responsibilities to maintain spiritual balance and communal cohesion.
- 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:15 p.m.