Triple

T31033771
Position Surface form Disambiguated ID Type / Status
Subject Coutts E790800 entity
Predicate hasBorderCrossingName P39988 FINISHED
Object Coutts–Sweetgrass Border Crossing 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: Coutts–Sweetgrass Border Crossing | Statement: [Coutts, hasBorderCrossingName, Coutts–Sweetgrass Border Crossing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderCrossingName
Context triple: [Coutts, hasBorderCrossingName, Coutts–Sweetgrass Border Crossing]
  • A. hasBorderCrossingSide
    Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
  • B. hasBorderCrossing
    Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
  • C. hasRailBorderCrossing
    Indicates that two places are connected by at least one official border crossing that is served by rail transport.
  • D. borderPostName chosen
    Indicates the specific name assigned to a border post where a boundary crossing or checkpoint is located.
  • E. hasBorderCrossingFunction
    Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
  • 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_69f224c97a788190b5da1ead6038a74e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fd09840ea88190a2e6d7e577ade717 completed May 7, 2026, 9:52 p.m.
PD Predicate disambiguation batch_69fd064c49988190afadddbd04d7cb94 completed May 7, 2026, 9:38 p.m.
Created at: April 29, 2026, 8:59 p.m.