Triple
T8665540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove Street (Wilmslow) |
E205662
|
entity |
| Predicate | hasPedestrianEnvironment |
P83965
|
FINISHED |
| Object | paved |
—
|
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: paved | Statement: [Grove Street (Wilmslow), hasPedestrianEnvironment, paved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianEnvironment Context triple: [Grove Street (Wilmslow), hasPedestrianEnvironment, paved]
-
A.
hasPedestrianArea
Indicates that a location or zone includes a designated area intended for pedestrian use only or primarily.
-
B.
hasPedestrianFunction
Indicates that an entity serves a role, purpose, or function specifically related to pedestrians or pedestrian use.
-
C.
hasPedestrianZoneStatus
Indicates whether an area or segment is designated as a pedestrian-only or pedestrian-priority zone and its corresponding status.
-
D.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
E.
hasPedestrianSteps
Indicates that one location or structure is connected to another by pedestrian steps or stairways.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a1dd1481908c56abca48fcd562 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.