Triple

T31938349
Position Surface form Disambiguated ID Type / Status
Subject Childress, Texas vicinity E815454 entity
Predicate nearestMajorCityDirection P68234 FINISHED
Object southeast of Amarillo, Texas LITERAL FINISHED

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: southeast of Amarillo, Texas | Statement: [Childress, Texas vicinity, nearestMajorCityDirection, southeast of Amarillo, Texas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearestMajorCityDirection
Context triple: [Childress, Texas vicinity, nearestMajorCityDirection, southeast of Amarillo, Texas]
  • A. nearestMajorCity
    Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
  • B. nearestCityTo
    Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
  • C. nearestMajorMetro chosen
    Indicates the relationship where a given location is associated with the closest large metropolitan area to it.
  • D. adjacentMajorCity
    Indicates that one major city is geographically next to or directly bordering another major city.
  • E. nearestRoadHead
    Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
  • 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_69f348f3035c81908558e2339955abb3 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f71f8ee0688190bd025f27993452d3 completed May 3, 2026, 10:12 a.m.
PD Predicate disambiguation batch_69f71cc405c08190863565609a4c8499 completed May 3, 2026, 10 a.m.
Created at: May 1, 2026, 12:05 a.m.