Triple
T4695367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1958 Agreement concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles |
E104128
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | vehicle regulation framework |
C11529
|
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: vehicle regulation framework Context triple: [1958 Agreement concerning the Adoption of Uniform Technical Prescriptions for Wheeled Vehicles, instanceOf, vehicle regulation framework]
-
A.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
-
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.
vehicle platform
A vehicle platform is a shared structural and mechanical foundation, including chassis, powertrain, and key components, upon which multiple vehicle models can be built.
-
D.
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.
-
E.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:17 p.m.