Triple
T25394058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheppard West station |
E636241
|
entity |
| Predicate | isNearStreet |
P8235
|
FINISHED |
| Object | Sheppard Avenue West |
—
|
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: Sheppard Avenue West | Statement: [Sheppard West station, isNearStreet, Sheppard Avenue West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNearStreet Context triple: [Sheppard West station, isNearStreet, Sheppard Avenue West]
-
A.
hasNearbyStreet
chosen
Indicates that one entity is located close to or adjacent to a street.
-
B.
hasNearbyStreetPattern
Indicates that one location has a street layout or configuration that is spatially close to, or in the vicinity of, another location’s street pattern.
-
C.
hasRoadProximity
Indicates that one entity is located near or adjacent to a road in terms of spatial proximity.
-
D.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
E.
hasNearbyTransportationCorridor
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5657379208190bd1ca0607af3e6c5 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.