Triple

T22639267
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 83 E558775 entity
Predicate terminusBLocation P149030 FINISHED
Object Canadian border near Westhope, North Dakota 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: Canadian border near Westhope, North Dakota | Statement: [U.S. Route 83, terminusBLocation, Canadian border near Westhope, North Dakota]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terminusBLocation
Context triple: [U.S. Route 83, terminusBLocation, Canadian border near Westhope, North Dakota]
  • A. terminusAdjacentTo
    Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
  • B. terminusBorough
    Indicates the borough in which the endpoint or terminus of something (such as a route or line) is located.
  • C. locatedAtTerminusOf
    Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
  • D. terminusEast
    Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
  • E. terminusSouthNear
    Indicates that the southern end or terminus of one entity is located close to another entity.
  • 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_69e24547f7fc819086e2c4ba3b979657 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17010aa4c8190a9f0cf7eb4c066cd completed April 29, 2026, 2:42 a.m.
PD Predicate disambiguation batch_69ee6294c4c08190b7e4829f4b9af24b completed April 26, 2026, 7:08 p.m.
PDg Predicate description generation batch_69ee8841e9cc81908d23b34215e3be71 completed April 26, 2026, 9:48 p.m.
Created at: April 17, 2026, 3:04 p.m.