Triple
T2040995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldergrove–Lynden border crossing |
E44743
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canada–United States border crossing |
C3197
|
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 crossing Context triple: [Aldergrove–Lynden border crossing, instanceOf, Canada–United States border crossing]
-
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.
state border crossing
A state border crossing is a designated point where people, vehicles, and goods are legally inspected and allowed to pass from one state or country into another.
-
C.
international border crossing
chosen
An international border crossing is a designated point where people, goods, and vehicles are legally inspected and allowed to pass between two countries.
-
D.
road border crossing
A road border crossing is a designated point along a roadway where vehicles and travelers legally pass between two jurisdictions or countries, typically featuring customs, immigration, and security controls.
-
E.
road–rail border crossing
A road–rail border crossing is a designated point at an international boundary where both road and railway transport routes intersect or pass through, enabling the controlled movement of vehicles, trains, goods, and passengers between neighboring countries.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:39 p.m.