Triple
T36393064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherbourne Street |
E896382
|
entity |
| Predicate | hasBikewayType |
P144329
|
FINISHED |
| Object | separated bike lanes |
—
|
LITERAL FINISHED |
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: separated bike lanes | Statement: [Sherbourne Street, hasBikewayType, separated bike lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBikewayType Context triple: [Sherbourne Street, hasBikewayType, separated bike lanes]
-
A.
bikeway
chosen
Indicates that there is a designated path or route intended primarily for bicycle travel between locations.
-
B.
hasBikewayTerminus
Indicates that a bikeway ends, terminates, or has its final point at the referenced location or entity.
-
C.
hasBicycleFacilities
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
D.
hasBicycleAccessFrom
Indicates that a location or entity can be reached from another location or entity specifically via bicycle access.
-
E.
bicycleType
Indicates the specific kind or category of bicycle associated with an 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.