Triple
T1562389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond–San Rafael Bridge |
E33354
|
entity |
| Predicate | hasBikePath |
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: [Richmond–San Rafael Bridge, hasBikePath, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBikePath Context triple: [Richmond–San Rafael Bridge, hasBikePath, 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.
hasWheelchairLanes
Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
-
D.
hasRailTrail
Indicates that one location or entity possesses, includes, or is connected by a rail trail (a recreational trail converted from or running along a former or existing railway corridor) to another location or entity.
-
E.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.