Triple
T25463265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiwol Chan Mat |
E638107
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya royal person |
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: Maya royal person Context triple: [Tiwol Chan Mat, instanceOf, Maya royal person]
-
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.
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.
-
C.
Maya royal regalia
Maya royal regalia comprises the elaborate garments, headdresses, jewelry, and symbolic objects worn by Maya rulers to display their divine authority, political power, and social status in ceremonial and public contexts.
-
D.
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.
-
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.
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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:13 p.m.