Triple
T10106822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision Zero San Francisco |
E216342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Vision Zero program |
C22284
|
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: Vision Zero program Context triple: [Vision Zero San Francisco, instanceOf, Vision Zero program]
-
A.
National Transportation Safety Board program
A National Transportation Safety Board program is an organized set of activities, policies, and resources designed to investigate transportation accidents, analyze safety data, and implement recommendations to improve national transportation safety.
-
B.
public transportation security program
A public transportation security program is a coordinated set of policies, technologies, and procedures designed to protect passengers, staff, and infrastructure across transit systems from threats, crime, and disruptions.
-
C.
public safety system
chosen
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
-
D.
autonomous vehicle project
An autonomous vehicle project is an organized effort to design, develop, test, and deploy self-driving systems that enable vehicles to perceive their environment, make driving decisions, and operate safely with minimal or no human intervention.
-
E.
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.
- 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.