Triple
T35026581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calgary–Medicine Hat |
E1010353
|
entity |
| Predicate | roadCorridorAlong |
P99514
|
FINISHED |
| Object | Trans-Canada Highway |
—
|
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: Trans-Canada Highway | Statement: [Calgary–Medicine Hat, roadCorridorAlong, Trans-Canada Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadCorridorAlong Context triple: [Calgary–Medicine Hat, roadCorridorAlong, Trans-Canada Highway]
-
A.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
B.
roadNameAlongRoute
chosen
Indicates that a specific road name is associated with, or used along, a particular segment or portion of a route.
-
C.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
D.
roadAxis
Indicates a central reference line that defines the primary longitudinal direction or alignment of a road.
-
E.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.