Triple

T36617847
Position Surface form Disambiguated ID Type / Status
Subject Lewiston–Queenston Border Crossing E903652 entity
Predicate tollChargedDirection P182158 FINISHED
Object Canada to United States 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: Canada to United States | Statement: [Lewiston–Queenston Border Crossing, tollChargedDirection, Canada to United States]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tollChargedDirection
Context triple: [Lewiston–Queenston Border Crossing, tollChargedDirection, Canada to United States]
  • A. noTollDirection
    Indicates that a specified direction or route segment does not require paying a toll.
  • B. tollingType
    Indicates the specific method or basis by which a toll, fee, or charge is applied or calculated in a given context.
  • C. tollCollectionSide chosen
    Indicates on which side (e.g., entry or exit, or direction of travel) a toll is collected in relation to a roadway or tolling point.
  • D. isTollRoadDestination
    Indicates that a location serves as a destination reachable via a toll road or requiring travel on a toll road to access it.
  • E. tollRoadOf
    Indicates that a road segment is a toll road belonging to or associated with a particular roadway, route, or transportation network.
  • 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_69f76e6960e4819092047756ceb9a17e completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c777e924819081a6634f549fe552 completed May 3, 2026, 10:08 p.m.
PD Predicate disambiguation batch_69f7c477a4d481908f52e55b6688f60c completed May 3, 2026, 9:56 p.m.
Created at: May 3, 2026, 4:11 p.m.