Triple

T33946003
Position Surface form Disambiguated ID Type / Status
Subject Saint Lawrence River crossing system E870291 entity
Predicate instanceOf P0 FINISHED
Object Canada–United States border infrastructure C47990 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: Canada–United States border infrastructure
Context triple: [Saint Lawrence River crossing system, instanceOf, Canada–United States border infrastructure]
  • A. U.S.–Mexico border crossing
    A U.S.–Mexico border crossing is a designated point of entry where people, vehicles, and goods are inspected and processed as they legally move between the United States and Mexico.
  • B. international border system chosen
    An international border system is the coordinated set of legal frameworks, physical infrastructures, technologies, and administrative processes that regulate the movement of people, goods, and information between sovereign states.
  • C. Border reiver
    A Border reiver is a lawless raider from the Anglo-Scottish borderlands between the late Middle Ages and early 17th century, known for cattle rustling, feuding, and shifting loyalties.
  • D. Panama Canal infrastructure
    Panama Canal infrastructure encompasses the system of locks, channels, dams, ports, support facilities, and control technologies that enable the transit, management, and maintenance of maritime traffic through the Panama Canal.
  • E. bridge in Canada
    A bridge in Canada is a structural crossing—such as a roadway, railway, or pedestrian span—located within Canadian territory that connects two points separated by physical obstacles like water, valleys, or other transportation routes.
  • F. None of above.

Provenance (1 batch)

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_69f3499b0dd48190b07b4b60babcee02 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:49 a.m.