Triple
T29216449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EPA Tier 5 emission standards |
E740679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposed emission standard |
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: proposed emission standard Context triple: [EPA Tier 5 emission standards, instanceOf, proposed emission standard]
-
A.
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.
-
B.
vehicle emissions regulator
A vehicle emissions regulator is a control device or system that monitors and adjusts engine operation to limit the pollutants released in a vehicle’s exhaust to meet environmental standards.
-
C.
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.
-
D.
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.
-
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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 12:13 p.m.