Triple
T33516611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Del Rio–Ciudad Acuña International Bridge |
E858382
|
entity |
| Predicate | stateOnMexicoSide |
P196335
|
FINISHED |
| Object | Coahuila |
—
|
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: Coahuila | Statement: [Del Rio–Ciudad Acuña International Bridge, stateOnMexicoSide, Coahuila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOnMexicoSide Context triple: [Del Rio–Ciudad Acuña International Bridge, stateOnMexicoSide, Coahuila]
-
A.
borderCityOnMexicanSide
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
B.
governingCountryForMexicanSide
Indicates the country that holds governing authority or jurisdiction over the Mexican side of a specified border, area, or context.
-
C.
isWalledCityNorthOfMexico
Indicates that a walled city is located geographically to the north of Mexico.
-
D.
includesMexicanStatePartially
Indicates that one entity contains some, but not all, of the territory or extent of a Mexican state.
-
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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 1, 2026, 1:39 a.m.