Triple
T30395187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coburn Gore border station |
E773196
|
entity |
| Predicate | roadAccessFromCanada |
P9041
|
FINISHED |
| Object | Quebec Route 161 |
—
|
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 Route 161 | Statement: [Coburn Gore border station, roadAccessFromCanada, Quebec Route 161]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadAccessFromCanada Context triple: [Coburn Gore border station, roadAccessFromCanada, Quebec Route 161]
-
A.
roadDirectionFromCanada
Indicates the direction in which a road extends or leads when traveling outward from Canada toward another location.
-
B.
roadOnCanadianSide
Indicates that the road is located on the Canadian side of a border or boundary.
-
C.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
D.
roadAccessVia
chosen
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
roadAccessCountryNetwork
Indicates that there exists a road-based transportation connection or accessibility between a country and a broader network of locations or routes.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685ac63248190a51b9e0e6ed89dab |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:02 p.m.