Triple
T31186382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buchanan Street, Glasgow |
E795054
|
entity |
| Predicate | isPedestrianPriorityZoneOf |
P46481
|
FINISHED |
| Object | Glasgow city centre |
—
|
NE NERFINISHED |
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: Glasgow city centre | Statement: [Buchanan Street, Glasgow, isPedestrianPriorityZoneOf, Glasgow city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPedestrianPriorityZoneOf Context triple: [Buchanan Street, Glasgow, isPedestrianPriorityZoneOf, Glasgow city centre]
-
A.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
B.
hasPedestrianZoneStatus
chosen
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
C.
isPedestrianGateway
Indicates that something serves as an access point or entrance specifically intended for use by pedestrians.
-
D.
isPedestrianFocus
Indicates that the primary attention or design consideration is directed toward pedestrians in a given context or environment.
-
E.
isInTrafficZone
Indicates that an entity is located within a designated traffic-regulated area or zone.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.