Triple
T29620471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City–Laredo corridor |
E754980
|
entity |
| Predicate | endPointBorderCity |
P15361
|
FINISHED |
| Object | Nuevo Laredo |
—
|
NE NERFINISHED |
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: Nuevo Laredo | Statement: [Mexico City–Laredo corridor, endPointBorderCity, Nuevo Laredo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endPointBorderCity Context triple: [Mexico City–Laredo corridor, endPointBorderCity, Nuevo Laredo]
-
A.
hasBorderCity
chosen
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
B.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
-
C.
countyBorder
Indicates that two counties share a common boundary or border with each other.
-
D.
bordersCityViaCoast
Indicates that a city is adjacent to a body of water in such a way that its boundary with that water forms part of the city’s coastal border.
-
E.
shareMajorBorderCities
Indicates that two regions or countries have a shared border along which there are one or more major cities situated on or near that boundary.
- F. None of above.
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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e24430081908f8731d6f52e0a2c |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:34 p.m.