Triple
T36495539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey Street |
E899175
|
entity |
| Predicate | servesPedestrianArea |
P18406
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Abbey Street, servesPedestrianArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesPedestrianArea Context triple: [Abbey Street, servesPedestrianArea, true]
-
A.
hasPedestrianArea
chosen
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
B.
hasPedestrianPlazaOn
Indicates that a pedestrian plaza is located on, or directly associated with, a specified surface, structure, or area.
-
C.
pedestrianizedAreas
Indicates areas where vehicle traffic is restricted or removed so that pedestrians have priority use of the space.
-
D.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasPedestrianZoneStatus
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: May 3, 2026, 4:10 p.m.