Triple
T16616694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocom Maya |
E403713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya dynasty |
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 dynasty Context triple: [Cocom Maya, instanceOf, Maya dynasty]
-
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.
Tamil dynasty
A Tamil dynasty is a ruling lineage originating from the Tamil-speaking regions of South India and Sri Lanka, characterized by its political authority, cultural patronage, and influence over Tamil society and history.
-
C.
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.
-
D.
Cham polity
Cham polity refers to the historical political entities and state structures formed by the Cham people in mainland Southeast Asia, particularly in what is now central and southern Vietnam, characterized by maritime trade, Hindu-Buddhist cultural influences, and shifting regional power dynamics.
-
E.
Burmese dynasty
A Burmese dynasty is a succession of rulers from the same family or lineage that governed regions of present-day Myanmar, shaping its political, cultural, and religious history over a defined historical period.
- 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.