Triple
T13570933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri Air Pollution Control Program |
E324157
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air pollution control program |
C6664
|
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 pollution control program Context triple: [Missouri Air Pollution Control Program, instanceOf, air pollution control program]
-
A.
air pollution control rule
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.
air quality permitting program
chosen
An air quality permitting program is a regulatory framework that evaluates, authorizes, and monitors facilities’ air emissions to ensure compliance with air pollution control standards and protect public health and the environment.
-
C.
air quality management plan
An air quality management plan is a structured framework of policies, strategies, and actions designed to monitor, control, and improve air quality to meet health and environmental standards.
-
D.
water pollution control program
A water pollution control program is an organized set of policies, regulations, monitoring activities, and treatment measures designed to prevent, reduce, and manage contaminants entering water bodies to protect human health and aquatic ecosystems.
-
E.
climate protection program
A climate protection program is an organized set of policies, actions, and measures designed to reduce greenhouse gas emissions, enhance climate resilience, and promote sustainable environmental practices.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:48 p.m.