Triple

T32391880
Position Surface form Disambiguated ID Type / Status
Subject Eagle Pass Port of Entry E827693 entity
Predicate adjacentCityInMexico P38816 FINISHED
Object Piedras Negras, 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: Piedras Negras, Coahuila | Statement: [Eagle Pass Port of Entry, adjacentCityInMexico, Piedras Negras, Coahuila]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: adjacentCityInMexico
Context triple: [Eagle Pass Port of Entry, adjacentCityInMexico, Piedras Negras, Coahuila]
  • A. adjacentMajorCity
    Indicates that one major city is geographically next to or directly bordering another major city.
  • B. adjacentCitySouth
    Indicates that one city is directly to the south of another city, sharing a common boundary or being immediately neighboring in that direction.
  • C. borderCityOnMexicanSide chosen
    Indicates that a city is located on the Mexican side of an international border shared with another country.
  • D. adjacentProvince
    Indicates that two provinces share a common boundary and are directly next to each other geographically.
  • E. adjacentCityNorth
    Indicates that one city is directly to the north of another city and shares a common boundary or is immediately neighboring it in that direction.
  • 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_69f349184e7481909c6c54428cb9cf12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f78fd5a6388190bfda4bbb2e222e5b completed May 3, 2026, 6:11 p.m.
PD Predicate disambiguation batch_69f78e2ac3fc819081a45c6841375c8d completed May 3, 2026, 6:04 p.m.
Created at: May 1, 2026, 12:52 a.m.