Triple
T25761388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osoyoos–Oroville border crossing |
E648747
|
entity |
| Predicate | roadLinkBetween |
P150509
|
FINISHED |
| Object | Canada |
—
|
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: Canada | Statement: [Osoyoos–Oroville border crossing, roadLinkBetween, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadLinkBetween Context triple: [Osoyoos–Oroville border crossing, roadLinkBetween, Canada]
-
A.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
B.
roadConnectionRegion
chosen
Indicates that a road provides a direct transportation connection between two regions.
-
C.
roadJunctionRelation
Indicates a spatial connection where two or more roads meet, intersect, or join at a junction.
-
D.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
E.
roadAssociatedWith
Indicates that there is a relevant connection or linkage between a road and another entity, such as use, location, function, or impact.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf06c588190bd5438a52bf1742c |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:05 a.m.