Triple
T369613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distillery District |
E8238
|
entity |
| Predicate | pedestrianStatus |
P6741
|
FINISHED |
| Object | pedestrian-only |
—
|
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: pedestrian-only | Statement: [Distillery District, pedestrianStatus, pedestrian-only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pedestrianStatus Context triple: [Distillery District, pedestrianStatus, pedestrian-only]
-
A.
pedestrianOnly
chosen
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
-
B.
hasSidewalk
Indicates that a location, path, or roadway is accompanied by a designated sidewalk area for pedestrian use.
-
C.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
D.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
E.
roadSignageIndicates
Indicates that a piece of road signage conveys, displays, or communicates specific information, instructions, or warnings about road conditions or regulations.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.