Triple
T25119878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanganxoán II |
E629236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Purépecha ruler |
C49744
|
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: Purépecha ruler Context triple: [Tanganxoán II, instanceOf, Purépecha ruler]
-
A.
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.
-
B.
Tepanec ruler
A Tepanec ruler was the sovereign leader of a Tepanec city-state in pre-Columbian central Mexico, wielding political, military, and religious authority over its people and territories.
-
C.
Aztec ruler
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.
-
D.
Toltec ruler
A Toltec ruler is the supreme political and religious leader of the Toltec civilization, responsible for governing the state, leading military campaigns, and overseeing major ceremonial and ritual activities.
-
E.
Palenque ruler
A Palenque ruler is a sovereign leader of the ancient Maya city-state of Palenque, responsible for political authority, religious rituals, military decisions, and the commissioning of monumental architecture and inscriptions.
- F. None of above. chosen
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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:27 a.m.