Triple
T10883566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strategic Highway Safety Plan |
E256983
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation safety plan |
C10081
|
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 safety plan Context triple: [Strategic Highway Safety Plan, instanceOf, transportation safety plan]
-
A.
aviation safety plan
An aviation safety plan is a structured, organization-wide framework that identifies hazards, assesses and mitigates risks, and defines procedures and responsibilities to ensure the safe operation of aviation activities.
-
B.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
C.
road transport contingency plan
A road transport contingency plan is a predefined set of strategies and procedures designed to maintain or quickly restore road-based logistics and mobility during disruptions, emergencies, or unexpected events.
-
D.
federal transportation safety guidance
chosen
Federal transportation safety guidance comprises the policies, recommendations, and standards issued by national authorities to prevent accidents, protect public welfare, and ensure safe operation across all modes of transportation.
-
E.
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.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.