Triple
T10106821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision Zero San Francisco |
E216342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic safety initiative |
C2546
|
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: traffic safety initiative Context triple: [Vision Zero San Francisco, instanceOf, traffic safety initiative]
-
A.
roadway safety guideline
A roadway safety guideline is a documented set of principles, rules, and recommended practices designed to minimize traffic-related risks and enhance the safety of all road users.
-
B.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
C.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
-
D.
traffic management scheme
A traffic management scheme is a coordinated set of policies, controls, and infrastructure measures designed to regulate and optimize the movement of vehicles, pedestrians, and goods within a transportation network.
-
E.
health and safety initiative
chosen
A health and safety initiative is a coordinated program of policies, practices, and interventions designed to prevent injuries and illnesses, promote well-being, and ensure a safe environment for individuals in a specific setting or community.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.