Triple
T38480839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puente Internacional Zaragoza |
E915668
|
entity |
| Predicate | borderCityOnMexicoSide |
P38816
|
FINISHED |
| Object | Ciudad Juárez |
—
|
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: Ciudad Juárez | Statement: [Puente Internacional Zaragoza, borderCityOnMexicoSide, Ciudad Juárez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCityOnMexicoSide Context triple: [Puente Internacional Zaragoza, borderCityOnMexicoSide, Ciudad Juárez]
-
A.
borderCityOnMexicanSide
chosen
Indicates that a city is located on the Mexican side of an international border shared with another country.
-
B.
borderCityOnUSSide
Indicates that a city is located on the U.S. side of an international border shared with another country.
-
C.
stateOnMexicoSide
Indicates that a state is located on the Mexican side of a shared border or boundary.
-
D.
borderTypeWithMexico
Indicates the type or nature of the border that an entity shares with Mexico.
-
E.
borderTownGuatemala
Indicates that a town is located on or near the national border of Guatemala, functioning as a border town relative to that 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 3, 2026, 4:31 p.m.