Triple
T33996616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 49 U.S.C. Chapter 301 |
E871688
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal motor vehicle safety statute |
C6692
|
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: federal motor vehicle safety statute Context triple: [49 U.S.C. Chapter 301, instanceOf, federal motor vehicle safety statute]
-
A.
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.
-
B.
FMCSA safety metric
A FMCSA safety metric is a quantitative measure used by the Federal Motor Carrier Safety Administration to evaluate and monitor the safety performance and regulatory compliance of commercial motor carriers and drivers.
-
C.
federal transportation safety guidance
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.
-
D.
federal law
chosen
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
-
E.
subtitle of federal transportation law
A subtitle of federal transportation law is a distinct, thematically organized subdivision within a broader transportation statute that groups related legal provisions under a common subject area.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.