Triple
T19094868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADN Regulations |
E467379
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dangerous goods transport regulations |
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: dangerous goods transport regulations Context triple: [ADN Regulations, instanceOf, dangerous goods transport regulations]
-
A.
dangerous goods declaration
A dangerous goods declaration is a formal document that provides detailed information and certification about hazardous materials in a shipment to ensure safe handling, transport, and regulatory compliance.
-
B.
shipping regulation
Shipping regulation is the set of laws, rules, and standards governing the safe, secure, and environmentally responsible operation of vessels and the transport of goods by sea and other waterways.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.