Triple
T15049218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Gate Bridge corridor |
E379309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pedestrian transportation corridor |
C3860
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: pedestrian transportation corridor Context triple: [Golden Gate Bridge corridor, instanceOf, pedestrian transportation corridor]
-
A.
pedestrian walkway
A pedestrian walkway is a designated path or corridor intended exclusively or primarily for people traveling on foot, providing safe and convenient passage separated from vehicular traffic.
-
B.
pedestrian network
A pedestrian network is an interconnected system of walkways, sidewalks, crossings, and paths designed to facilitate safe and efficient movement of people on foot within and between areas.
-
C.
pedestrian bridge
chosen
A pedestrian bridge is a raised structure designed exclusively for people on foot (and often cyclists) to safely cross obstacles such as roads, railways, or waterways without interacting with vehicular traffic.
-
D.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
-
E.
pedestrian-oriented commercial district
A pedestrian-oriented commercial district is a compact, walkable area where shops, services, and public spaces are clustered and designed primarily for people on foot rather than for automobile access.
- F. None of above.
Provenance (1 batch)
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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3 a.m.