Triple
T1444821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NESHAP |
E31153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental regulation |
C1116
|
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: environmental regulation Context triple: [NESHAP, instanceOf, environmental regulation]
-
A.
environmental governance instrument
chosen
An environmental governance instrument is a policy tool, mechanism, or institutional arrangement used by public or private actors to influence behaviors and decisions in order to protect, manage, or restore the environment.
-
B.
environmental programme
An environmental programme is an organized set of coordinated activities, policies, and initiatives designed to protect, manage, or improve the natural environment and promote sustainable practices.
-
C.
state environmental protection agency
A state environmental protection agency is a government body responsible for developing, implementing, and enforcing policies and regulations to protect and improve the state's air, water, land, and natural resources.
-
D.
environmental management division
The environmental management division is an organizational unit responsible for planning, implementing, and overseeing policies and programs that protect the environment, ensure regulatory compliance, and promote sustainable use of natural resources.
-
E.
environmental cleanup agreement
An environmental cleanup agreement is a legally binding contract in which parties define responsibilities, standards, timelines, and cost allocations for investigating, remediating, and monitoring contamination at a specific site.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.