Triple
T23990354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster, Ontario |
E605044
|
entity |
| Predicate | nearbyHighwayExit |
P16027
|
FINISHED |
| Object | Ontario Highway 401 exit for Lancaster |
—
|
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: Ontario Highway 401 exit for Lancaster | Statement: [Lancaster, Ontario, nearbyHighwayExit, Ontario Highway 401 exit for Lancaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyHighwayExit Context triple: [Lancaster, Ontario, nearbyHighwayExit, Ontario Highway 401 exit for Lancaster]
-
A.
nearbyHighwayMilepost
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
B.
motorwayJunctionNearby
chosen
Indicates that a motorway junction is located close to the referenced entity.
-
C.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
-
D.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
E.
nearestTurnpikeInterchange
Indicates that one location is the closest turnpike interchange to another specified location.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38b37648190afb003cded3a7484 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:37 p.m.