Triple
T24819283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennelong Bridge |
E621014
|
entity |
| Predicate | footpath |
P127139
|
FINISHED |
| Object | shared pedestrian and cycle path on one side |
—
|
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: shared pedestrian and cycle path on one side | Statement: [Bennelong Bridge, footpath, shared pedestrian and cycle path on one side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footpath Context triple: [Bennelong Bridge, footpath, shared pedestrian and cycle path on one side]
-
A.
footpathWidth
Indicates the measured or designated width of a footpath in the context of a spatial or infrastructural relationship.
-
B.
hasFootways
Indicates that something includes or is connected to designated footpaths or pedestrian walkways.
-
C.
walkwayType
chosen
Indicates the specific kind or classification of a walkway associated with an entity (e.g., sidewalk, footpath, boardwalk).
-
D.
bikeway
Indicates that there is a designated path or route intended primarily for bicycle travel between locations.
-
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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:04 a.m.