Triple
T16616726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiu Maya |
E403714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya noble lineage |
C28207
|
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 noble lineage Context triple: [Xiu Maya, instanceOf, Maya noble lineage]
-
A.
Maya royal dynasty
chosen
A Maya royal dynasty is a hereditary ruling lineage that governed a Maya city-state, legitimized its authority through divine ancestry, and oversaw political, religious, and military affairs across generations.
-
B.
Maya people
The Maya people are an indigenous Mesoamerican civilization known for their advanced writing system, mathematics, astronomy, and monumental architecture, with descendants who continue to maintain rich cultural traditions across present-day Mexico and Central America.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.