Triple
T27459989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carway border crossing |
E692707
|
entity |
| Predicate | roadDirectionFromUS |
P44884
|
FINISHED |
| Object | northbound to Alberta |
—
|
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: northbound to Alberta | Statement: [Carway border crossing, roadDirectionFromUS, northbound to Alberta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDirectionFromUS Context triple: [Carway border crossing, roadDirectionFromUS, northbound to Alberta]
-
A.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
B.
roadDirectionConvention
Indicates the customary rule in a place for which side of the road vehicles are expected to drive on.
-
C.
locationDirection
Indicates that one entity is located in a specific directional relation (such as north, south, above, or below) relative to another entity.
-
D.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
-
E.
hasStreetDirection
chosen
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:49 p.m.