Triple
T37792211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Markets Program Data |
E942114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air emissions database |
C6669
|
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: air emissions database Context triple: [Air Markets Program Data, instanceOf, air emissions database]
-
A.
pollutant release and transfer register
A pollutant release and transfer register is a publicly accessible database that systematically records the quantities of specific pollutants released to air, water, and land, or transferred off-site for treatment or disposal, by industrial and other facilities.
-
B.
environmental database
chosen
An environmental database is a structured collection of data related to natural resources, ecosystems, pollution, climate, and other environmental factors, designed to support analysis, monitoring, and decision-making.
-
C.
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.
-
D.
mobile source emissions model
A mobile source emissions model is a computational framework that estimates air pollutant and greenhouse gas emissions produced by on-road and off-road mobile sources (such as cars, trucks, and construction equipment) under varying operating and environmental conditions.
-
E.
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.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.