Triple
T5445825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riviera Maya |
E122245
|
entity |
| Predicate | hasArchaeologicalSite |
P1098
|
FINISHED |
| Object | Cobá |
E49046
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cobá | Statement: [Riviera Maya, hasArchaeologicalSite, Cobá]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cobá Context triple: [Riviera Maya, hasArchaeologicalSite, Cobá]
-
A.
Cobá
chosen
Cobá is an ancient Maya city in Mexico’s Yucatán Peninsula, known for its extensive network of sacbeob (raised stone roads) and towering pyramid structures amid dense jungle.
-
B.
Comalcalco
Comalcalco is a city in the Mexican state of Tabasco known for its nearby Maya archaeological site built with brick structures.
-
C.
Nojpetén
Nojpetén was the last independent Maya capital city, located on an island in Lake Petén Itzá in present-day Guatemala.
-
D.
Coacalco
Coacalco is a suburban municipality in the State of Mexico that forms part of the greater Mexico City metropolitan area.
-
E.
Sayula Popoluca
Sayula Popoluca is an indigenous Mixe–Zoquean language spoken by a small community in the region of Sayula, Veracruz, Mexico.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69bd4640f52c81909e653ec361f66d76 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd91cf5d488190868ffefad02c7a04 |
completed | March 20, 2026, 6:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf413573c08190beae400c485d2132 |
completed | March 22, 2026, 1:09 a.m. |
Created at: March 20, 2026, 2:07 p.m.