Triple
T38690583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedras Negras–Eagle Pass border crossing |
E949250
|
entity |
| Predicate | borderMunicipalityOnMexicanSide |
P202008
|
FINISHED |
| Object | Piedras Negras Municipality |
—
|
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: Piedras Negras Municipality | Statement: [Piedras Negras–Eagle Pass border crossing, borderMunicipalityOnMexicanSide, Piedras Negras Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderMunicipalityOnMexicanSide Context triple: [Piedras Negras–Eagle Pass border crossing, borderMunicipalityOnMexicanSide, Piedras Negras Municipality]
-
A.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
B.
borderTypeWithMexico
Indicates the type or nature of the border that an entity shares with Mexico.
-
C.
bordersMexicanState
Indicates that one entity shares a land or maritime boundary with a state of Mexico.
-
D.
stateOnMexicoSide
Indicates that a state is located on the Mexican side of a shared border or boundary.
-
E.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
- F. None of above. chosen
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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0042524d8c8190884a10fce669ae95 |
completed | May 10, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_6a0041e89bd881909e32764699bcb89b |
completed | May 10, 2026, 8:29 a.m. |
| PDg | Predicate description generation | batch_6a004251a1308190aa523d5365eeb9f7 |
completed | May 10, 2026, 8:31 a.m. |
Created at: May 3, 2026, 4:33 p.m.