Triple
T17994389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tizoc |
E430462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mexica ruler |
C5985
|
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: Mexica ruler Context triple: [Tizoc, instanceOf, Mexica ruler]
-
A.
Aztec ruler
chosen
An Aztec ruler was the supreme political, military, and religious leader of the Aztec Empire, responsible for governing the state, leading armies, overseeing tribute, and serving as an intermediary with the gods.
-
B.
Aztec emperor
An Aztec emperor is the supreme political, military, and religious ruler of the Aztec Empire, responsible for governing the state, leading armies, overseeing tribute, and serving as the primary intermediary between the gods and the people.
-
C.
Totonac ruler
A Totonac ruler is the sovereign leader of a Totonac city-state or polity, responsible for political authority, religious duties, military command, and the administration of tribute and justice within Totonac society.
-
D.
tlatoani of Tenochtitlan
The tlatoani of Tenochtitlan was the supreme ruler and political, military, and religious leader of the Mexica (Aztec) capital city-state, governing its affairs and representing its authority within the broader Aztec Empire.
-
E.
Maya ruler
A Maya ruler was the hereditary political and religious leader of a Maya city-state, responsible for governance, warfare, ritual performance, and maintaining divine favor for the community.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
Created at: April 10, 2026, 10:23 a.m.