Triple
T22327761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Transit-First Policy |
E551944
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation policy |
C19343
|
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: transportation policy Context triple: [San Francisco Transit-First Policy, instanceOf, transportation policy]
-
A.
transport policy report
A transport policy report is a structured document that analyzes current transportation systems, evaluates policy options, and presents evidence-based recommendations to guide decision-making in the transport sector.
-
B.
transport policy framework
chosen
A transport policy framework is a structured set of principles, goals, and regulatory tools that guide the planning, funding, operation, and governance of transportation systems to achieve economic, social, and environmental objectives.
-
C.
transport sector
The transport sector encompasses all systems, services, and infrastructure involved in moving people and goods by road, rail, air, and water.
-
D.
public transportation infrastructure
Public transportation infrastructure encompasses the physical and organizational systems—such as buses, trains, stations, tracks, and supporting facilities—that enable the efficient movement of people via shared transit services.
-
E.
transport policy body
A transport policy body is an organization or authority responsible for developing, coordinating, and overseeing regulations, strategies, and standards that govern transportation systems and services.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.