Triple
T31303364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brixton Splash |
E798267
|
entity |
| Predicate | streetUsage |
P172214
|
FINISHED |
| Object | closed streets for pedestrians |
—
|
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: closed streets for pedestrians | Statement: [Brixton Splash, streetUsage, closed streets for pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetUsage Context triple: [Brixton Splash, streetUsage, closed streets for pedestrians]
-
A.
roadUse
Indicates that an entity utilizes or travels on a particular road or roadway for movement or transport.
-
B.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
C.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
D.
touristTraffic
Indicates the level, flow, or intensity of tourists visiting or moving through a particular place or area.
-
E.
trafficUseOutsideEvents
Indicates that the traffic-related resource or arrangement is used during times when no special events are taking place.
- F. None of above. chosen
Provenance (4 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 29, 2026, 9:14 p.m.