Triple
T558008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Environmental Remediation |
E11986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental remediation organization |
C6
|
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 remediation organization Context triple: [Division of Environmental Remediation, instanceOf, environmental remediation organization]
-
A.
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.
-
B.
Superfund site
A Superfund site is a contaminated location in the United States designated by the Environmental Protection Agency for long-term cleanup of hazardous substances and pollutants under the Superfund program.
-
C.
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.
-
D.
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.
-
E.
nonprofit organization
chosen
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.