Triple
T27459988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carway border crossing |
E692707
|
entity |
| Predicate | roadDirectionFromCanada |
P163492
|
FINISHED |
| Object | southbound to Montana |
—
|
LITERAL FINISHED |
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: southbound to Montana | Statement: [Carway border crossing, roadDirectionFromCanada, southbound to Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDirectionFromCanada Context triple: [Carway border crossing, roadDirectionFromCanada, southbound to Montana]
-
A.
roadOnCanadianSide
Indicates that the road is located on the Canadian side of a border or boundary.
-
B.
directionFromOttawa
Indicates the cardinal or relative compass direction in which one entity is located from Ottawa.
-
C.
directionFromEdmonton
Indicates the compass direction or relative bearing of one place or object as measured outward from Edmonton.
-
D.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
-
E.
borderDirectionRelativeToCalgary
Indicates the directional orientation of a border relative to the location of Calgary.
- F. None of above. chosen
Provenance (4 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 12:49 p.m.