Triple
T7921833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellowhead Highway |
E183961
|
entity |
| Predicate | routeNumberInSaskatchewan |
P1864
|
FINISHED |
| Object | Highway 16 |
—
|
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: Highway 16 | Statement: [Yellowhead Highway, routeNumberInSaskatchewan, Highway 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNumberInSaskatchewan Context triple: [Yellowhead Highway, routeNumberInSaskatchewan, Highway 16]
-
A.
routeNumber
chosen
Indicates the specific identifying number assigned to a route within a transportation or delivery network.
-
B.
parentRouteNumber
Indicates that one route is the immediate higher-level or containing route from which another route is derived or subordinated.
-
C.
northSouthRoutes
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
D.
routeNumberFormat
Indicates how the identifying number or code for a route is structured or formatted.
-
E.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9499cc8190b6bd81f4625c77ab |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.