Triple

T33046349
Position Surface form Disambiguated ID Type / Status
Subject Progreso, Yucatán E845606 entity
Predicate connectedBy P37 FINISHED
Object Progreso–Mérida road
The Progreso–Mérida road is a major highway in the Mexican state of Yucatán that links the coastal port city of Progreso with the inland state capital, Mérida.
E2033312 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–Mérida road | Statement: [Progreso, Yucatán, connectedBy, Progreso–Mérida road]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Progreso–Mérida road
Triple: [Progreso, Yucatán, connectedBy, Progreso–Mérida road]
Generated description
The Progreso–Mérida road is a major highway in the Mexican state of Yucatán that links the coastal port city of Progreso with the inland state capital, Mérida.

Provenance (5 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_69f3495242e48190996a2cb2beab5455 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d3154e5481908e767af98b4158cf completed May 3, 2026, 4:46 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34e5181dc481908dc4eb3229d81399 completed June 19, 2026, 6:43 a.m.
NEDg Description generation batch_6a34e59acd3881909553f0183936d6c3 completed June 19, 2026, 6:45 a.m.
NED2 Entity disambiguation (via description) batch_6a34e636e39c81908868854b86b84bed completed June 19, 2026, 6:48 a.m.
Created at: May 1, 2026, 1:24 a.m.