Triple
T38693258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitt Street Mall |
E949926
|
entity |
| Predicate | hasPedestrianAccessRestriction |
P28318
|
FINISHED |
| Object | no private vehicle traffic |
—
|
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: no private vehicle traffic | Statement: [Pitt Street Mall, hasPedestrianAccessRestriction, no private vehicle traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianAccessRestriction Context triple: [Pitt Street Mall, hasPedestrianAccessRestriction, no private vehicle traffic]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
pedestrianRestrictions
chosen
Indicates that there are specific rules or limitations governing where or how pedestrians may travel or access an area.
-
C.
hasPedestrianZoneStatus
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
D.
closedToPedestrians
Indicates that access along the specified route or area is prohibited for pedestrians.
-
E.
pedestrianOnly
Indicates that a path, area, or route is designated exclusively for pedestrians and prohibits vehicle access.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:33 p.m.