Triple
T5076566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westferry Circus |
E114410
|
entity |
| Predicate | hasPedestrianFunction |
P61279
|
FINISHED |
| Object | provides landscaped walking routes |
—
|
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: provides landscaped walking routes | Statement: [Westferry Circus, hasPedestrianFunction, provides landscaped walking routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianFunction Context triple: [Westferry Circus, hasPedestrianFunction, provides landscaped walking routes]
-
A.
hasPedestrianCharacter
Indicates that something possesses qualities, features, or behavior characteristic of pedestrians or pedestrian use.
-
B.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
C.
hasPedestrianPhase
Indicates that a traffic signal includes a dedicated phase during which pedestrians are allowed to cross.
-
D.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
E.
hasPedestrianArea
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d3b0088190a658864cb120eef4 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.