Triple
T26182966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaxun Bʼalam IV |
E654737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Classic Maya king |
C20715
|
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: Classic Maya king Context triple: [Yaxun Bʼalam IV, instanceOf, Classic Maya king]
-
A.
Maya ruler
chosen
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.
-
B.
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.
-
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.
Mixtec ruler
A Mixtec ruler is the hereditary or appointed leader of a Mixtec city-state who exercised political, military, religious, and economic authority within pre-Columbian and early colonial Mixtec society.
-
E.
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.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:41 p.m.