Triple
T25464667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truck and Bus Regulation |
E638141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diesel emissions rule |
C20932
|
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: diesel emissions rule Context triple: [Truck and Bus Regulation, instanceOf, diesel emissions rule]
-
A.
air pollution control rule
chosen
An air pollution control rule is a regulatory requirement that limits or manages the emission of pollutants into the air from specific sources to protect public health and the environment.
-
B.
emissions control zone
An emissions control zone is a designated geographic area where stricter limits on air pollutants are enforced to reduce environmental and health impacts from sources such as vehicles, ships, and industrial activities.
-
C.
vehicle noise emission regulation
Vehicle noise emission regulation is a set of legal standards and technical requirements that limit the permissible sound levels produced by vehicles to reduce environmental noise and protect public health.
-
D.
emissions allowance
An emissions allowance is a tradable permit that authorizes its holder to emit a specified quantity of a pollutant, typically within a regulated cap-and-trade or similar environmental compliance system.
-
E.
port emissions reduction initiative
A port emissions reduction initiative is a coordinated program of policies, technologies, and operational changes designed to lower air pollutants and greenhouse gas emissions from maritime, terminal, and landside activities within and around a port.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:14 p.m.