Triple
T38690584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piedras Negras–Eagle Pass border crossing |
E949250
|
entity |
| Predicate | borderCountyOnUSSide |
P149057
|
FINISHED |
| Object | Maverick County, Texas |
—
|
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: Maverick County, Texas | Statement: [Piedras Negras–Eagle Pass border crossing, borderCountyOnUSSide, Maverick County, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCountyOnUSSide Context triple: [Piedras Negras–Eagle Pass border crossing, borderCountyOnUSSide, Maverick County, Texas]
-
A.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
-
B.
countyBorder
chosen
Indicates that two counties share a common boundary or border with each other.
-
C.
borderStateOnUSSide
Indicates that a state is located on the U.S. side of an international border shared with another country.
-
D.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
E.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0045a7b4c081908e4dedabda7cf790 |
completed | May 10, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_6a0042b148a48190974b173f352e4b7f |
completed | May 10, 2026, 8:32 a.m. |
Created at: May 3, 2026, 4:33 p.m.