Triple
T6206020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 15th Street NW |
E138748
|
entity |
| Predicate | bikeLaneType |
P31631
|
FINISHED |
| Object | protected two-way cycle track (on portions) |
—
|
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: protected two-way cycle track (on portions) | Statement: [15th Street NW, bikeLaneType, protected two-way cycle track (on portions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bikeLaneType Context triple: [15th Street NW, bikeLaneType, protected two-way cycle track (on portions)]
-
A.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
B.
bicyclesAllowed
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
-
C.
hasDedicatedLanes
chosen
Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
-
D.
bicycleType
Indicates the specific kind or category of bicycle associated with an entity.
-
E.
beltwayType
Indicates the specific classification or type of a beltway (ring road) associated with a given roadway or area.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626f85748190a94448117a85fd78 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.