Triple
T33276425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puuc archaeological zone |
E851919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maya archaeological site group |
C58564
|
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 archaeological site group Context triple: [Puuc archaeological zone, instanceOf, Maya archaeological site group]
-
A.
Mixtec archaeological site
A Mixtec archaeological site is a location containing material remains, architecture, and artifacts associated with the pre-Columbian Mixtec civilization, offering evidence of their social, political, religious, and economic life.
-
B.
Maya palace group
A Maya palace group is a complex of interconnected residential, administrative, and ceremonial structures that served as the political and social center for elite rulers in a Maya city.
-
C.
Olmec site
An Olmec site is an archaeological location associated with the Olmec civilization, characterized by monumental stone sculptures, ceremonial centers, and evidence of early Mesoamerican cultural development.
-
D.
Maya monument
A Maya monument is a large, often intricately carved architectural or sculptural structure created by the ancient Maya civilization to commemorate rulers, deities, historical events, or cosmological beliefs.
-
E.
Mesoamerican architectural site feature
A Mesoamerican architectural site feature is a distinct structural or spatial element—such as pyramids, ballcourts, plazas, or causeways—integral to the layout, function, and symbolism of ancient Mesoamerican ceremonial and urban centers.
- F. None of above. chosen
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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.