Triple
T11733307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzibilchaltún |
E278955
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Progreso |
E260099
|
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: Progreso | Statement: [Dzibilchaltún, locatedNear, Progreso]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Progreso Context triple: [Dzibilchaltún, locatedNear, Progreso]
-
A.
Progreso
chosen
Progreso is a coastal port city in the Mexican state of Yucatán, known as a gateway for cruise ships and access point to nearby Mayan archaeological sites.
-
B.
Álamos
Álamos is a residential neighborhood in Mexico City’s Benito Juárez borough, known for its central location and urban character.
-
C.
Ciudad Delgado
Ciudad Delgado is an urban municipality in El Salvador that forms part of the metropolitan area of San Salvador.
-
D.
Colonia Morelos
Colonia Morelos is a neighborhood in the Cuauhtémoc borough of Mexico City, known for its dense urban character and proximity to the historic center.
-
E.
Colonia Juárez
Colonia Juárez is a historic and centrally located neighborhood in Mexico City known for its eclectic architecture, cultural venues, and vibrant commercial and nightlife scenes.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4daa7f48190896fc7653e9dd70b |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ef8406fe8881909722ecb040087e68 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 8, 2026, 9:41 p.m.