Triple
T11844293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Federal Highway 57 |
E281731
|
entity |
| Predicate | servesEconomicCorridor |
P77611
|
FINISHED |
| Object | Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor |
E845910
|
NE FINISHED |
How this triple was built (3 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: Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor | Statement: [Mexican Federal Highway 57, servesEconomicCorridor, Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor Context triple: [Mexican Federal Highway 57, servesEconomicCorridor, Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor]
-
A.
Mexico City–Monterrey corridor
The Mexico City–Monterrey corridor is a major transportation and economic axis in northeastern and central Mexico, linking the capital with the industrial hub of Monterrey through key intermediate cities.
-
B.
Mexico City–Querétaro corridor
chosen
The Mexico City–Querétaro corridor is a major economic and transportation axis in central Mexico that links the capital with the industrial city of Querétaro and numerous intermediate urban centers.
-
C.
Mexico City–Acapulco corridor
The Mexico City–Acapulco corridor is a major transportation route in Mexico that links the nation’s capital with the Pacific coastal resort city of Acapulco, serving as a key axis for tourism and commerce.
-
D.
Mexico City–Laredo corridor
The Mexico City–Laredo corridor is a major transportation route in Mexico that links the capital, Mexico City, with the U.S. border city of Nuevo Laredo, serving as a key axis for trade and travel between the two countries.
-
E.
Veracruz–Mexico City route
The Veracruz–Mexico City route was a crucial 19th-century corridor linking Mexico’s principal Gulf Coast port to its capital, making it a key strategic axis in military campaigns such as the Mexican–American War.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesEconomicCorridor Context triple: [Mexican Federal Highway 57, servesEconomicCorridor, Mexico City–Querétaro–San Luis Potosí–Saltillo–Monterrey corridor]
-
A.
partOfEconomicCorridor
chosen
Indicates that one entity is included within, or constitutes a segment of, a larger defined economic corridor.
-
B.
isIndustrialCorridor
Indicates that an area or route is designated and used primarily for industrial activities, facilities, or transportation.
-
C.
locatedInTransportCorridor
Indicates that an entity is situated within a designated transport corridor used for the movement of people or goods.
-
D.
partOfTransportCorridorTo
Indicates that one entity forms a component or segment of a larger transport corridor leading to another entity.
-
E.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
- F. None of above.
Provenance (4 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65a597c8190b09f57463b279afc |
completed | April 10, 2026, 7:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f2814210e48190821fca390dc7e312 |
completed | April 29, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.