Triple
T18801244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walterdale Bridge (Edmonton) |
E459755
|
entity |
| Predicate | hasNonMotorizedFacility |
P1709
|
FINISHED |
| Object | multi-use trail |
—
|
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: multi-use trail | Statement: [Walterdale Bridge (Edmonton), hasNonMotorizedFacility, multi-use trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonMotorizedFacility Context triple: [Walterdale Bridge (Edmonton), hasNonMotorizedFacility, multi-use trail]
-
A.
isNonMotorized
Indicates that the entity does not use a motor for propulsion or operation.
-
B.
hasBicycleFacilities
chosen
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
C.
bicyclesAllowed
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
-
D.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
E.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02332d88190b68feea7f2f86d06 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.