Triple
T32432131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Nuevo Laredo |
E828752
|
entity |
| Predicate | borderOppositeCity |
P78863
|
FINISHED |
| Object | Laredo, 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: Laredo, Texas | Statement: [Diocese of Nuevo Laredo, borderOppositeCity, Laredo, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderOppositeCity Context triple: [Diocese of Nuevo Laredo, borderOppositeCity, Laredo, Texas]
-
A.
oppositeTownAcrossBorder
chosen
Indicates that one town is located directly across a border from another town, positioned as its opposite counterpart.
-
B.
hasBorderCity
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
C.
cityIsBorderCity
Indicates that a city is located on or near a boundary between two regions, countries, or administrative areas.
-
D.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
-
E.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: May 1, 2026, 12:55 a.m.