Triple
T35235810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedras Negras royal dynasty |
E1017372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Classic period Maya polity leadership |
C47517
|
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 period Maya polity leadership Context triple: [Piedras Negras royal dynasty, instanceOf, Classic period Maya polity leadership]
-
A.
Mesoamerican nobility
Mesoamerican nobility comprised the hereditary elite classes of pre-Columbian societies, who held political, religious, and military authority, controlled land and tribute, and maintained social hierarchy through lineage, ritual, and alliance.
-
B.
highland Maya state
A highland Maya state is a politically centralized society in the mountainous regions of the Maya area, characterized by hierarchical governance, urban centers, intensive agriculture, and complex religious and economic institutions.
-
C.
Maya royal dynasty
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.
-
D.
pre-Columbian polity
chosen
A pre-Columbian polity is a socially and politically organized group or state that existed in the Americas before European contact, characterized by its own systems of governance, economy, and culture.
-
E.
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.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.