Triple
T26780856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Bernard-de-Lacolle |
E670241
|
entity |
| Predicate | borderCrossingOnHighway |
P113301
|
FINISHED |
| Object | Quebec Autoroute 15 |
—
|
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: Quebec Autoroute 15 | Statement: [Saint-Bernard-de-Lacolle, borderCrossingOnHighway, Quebec Autoroute 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCrossingOnHighway Context triple: [Saint-Bernard-de-Lacolle, borderCrossingOnHighway, Quebec Autoroute 15]
-
A.
borderPostLocatedOnHighway
chosen
Indicates that a border control post is situated along or directly on a specific highway.
-
B.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
C.
borderCrossingRouteTo
Indicates a route or path used to travel across a border from one place or jurisdiction to another.
-
D.
crossesInternationalBoundaryAt
Indicates that one entity passes from one country’s territory into another at a specific boundary location.
-
E.
usesBorderCrossing
Indicates that one entity makes use of a specific border crossing point to pass from one jurisdiction or territory to another.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 4:09 a.m.