Triple
T4695318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Technical Regulations under the 1998 Agreement |
E104127
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road vehicle safety regulation |
C10033
|
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: road vehicle safety regulation Context triple: [Global Technical Regulations under the 1998 Agreement, instanceOf, road vehicle safety regulation]
-
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.
safety regulation
chosen
A safety regulation is a formal rule or standard established by authorities or organizations to prevent harm, reduce risk, and protect people, property, and the environment in specific activities or industries.
-
C.
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.
-
D.
highway law
Highway law is the body of legal rules and regulations governing the construction, maintenance, use, and safety of public roads and highways, including the rights and responsibilities of authorities and road users.
-
E.
rail safety legislation
Rail safety legislation comprises the laws and regulations that govern the safe design, operation, maintenance, and oversight of railway systems to protect passengers, workers, and the public.
- 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.