Triple
T11537317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosciuszko Bridge |
E273582
|
entity |
| Predicate | hasBicyclePedestrianPath |
P1709
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kosciuszko Bridge, hasBicyclePedestrianPath, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBicyclePedestrianPath Context triple: [Kosciuszko Bridge, hasBicyclePedestrianPath, yes]
-
A.
hasBicycleFacilities
chosen
Indicates that appropriate bicycle-related infrastructure or amenities are available at or associated with the subject.
-
B.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
C.
hasBikewayTerminus
Indicates that a bikeway ends, terminates, or has its final point at the referenced location or entity.
-
D.
bicyclesAllowed
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
-
E.
pedestrianFriendly
Indicates that an environment, route, or area is designed or suitable for safe, comfortable, and convenient use by pedestrians.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.