Triple
T30809442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Farleigh Bridge |
E784600
|
entity |
| Predicate | hasPedestrianProvision |
P129016
|
FINISHED |
| Object | no separate footpath |
—
|
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 separate footpath | Statement: [East Farleigh Bridge, hasPedestrianProvision, no separate footpath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianProvision Context triple: [East Farleigh Bridge, hasPedestrianProvision, no separate footpath]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
hasPedestrianSections
chosen
Indicates that an object (such as a route, road, or area) includes one or more sections specifically designated for pedestrian use.
-
C.
hasPedestrianArea
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
D.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
E.
hasPedestrianFunction
Indicates that an entity serves a role, purpose, or function specifically related to pedestrians or pedestrian use.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 8:43 p.m.