Triple
T8636335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Massey Tunnel |
E204530
|
entity |
| Predicate | nearbyInterchange |
P33739
|
FINISHED |
| Object | Highway 17A |
—
|
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 17A | Statement: [George Massey Tunnel, nearbyInterchange, Highway 17A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyInterchange Context triple: [George Massey Tunnel, nearbyInterchange, Highway 17A]
-
A.
hasNearbyInterchange
chosen
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
-
B.
motorwayJunctionNearby
Indicates that a motorway junction is located close to the referenced entity.
-
C.
nearestInterstateHighway
Indicates that one interstate highway is the closest in distance to a given location or route compared to all other interstate highways.
-
D.
nearJunctionOf
Indicates that one entity is located close to the point where two or more linear features (such as roads, tracks, or paths) meet or intersect.
-
E.
nearInterstate
Indicates that one entity is located close to or in the immediate vicinity of an interstate highway.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.