Triple
T27208364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple III at Tikal |
E683933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Classic-period Maya monument |
C22874
|
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 monument Context triple: [Temple III at Tikal, instanceOf, Classic-period Maya monument]
-
A.
Maya monument
chosen
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.
-
B.
Maya ceremonial platform
A Maya ceremonial platform is an elevated, often rectangular structure used as a sacred stage for rituals, offerings, and public religious performances within Maya civic-ceremonial centers.
-
C.
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.
-
D.
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.
-
E.
Mesoamerican architecture
Mesoamerican architecture encompasses the monumental and ceremonial building traditions of pre-Columbian cultures in Central America, characterized by stepped pyramids, plazas, ballcourts, intricate stone carvings, and precise astronomical alignments.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:38 a.m.