Triple
T7242729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCOR |
E156395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental cleanup contractor |
C13667
|
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 cleanup contractor Context triple: [UCOR, instanceOf, environmental cleanup contractor]
-
A.
environmental cleanup law
Environmental cleanup law governs the responsibilities, procedures, and standards for identifying, remediating, and preventing contamination of land, water, and air to protect public health and ecosystems.
-
B.
environmental cleanup fund
An environmental cleanup fund is a dedicated pool of financial resources established to pay for the assessment, remediation, and long-term management of contaminated sites and environmental damage.
-
C.
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.
-
D.
environmental protection occupation
chosen
An environmental protection occupation involves work focused on preserving, restoring, and managing natural resources and ecosystems to prevent pollution, reduce environmental harm, and promote sustainability.
-
E.
environmental protection unit
An environmental protection unit is an organized group or division dedicated to monitoring, preserving, and improving the natural environment by enforcing regulations, mitigating pollution, and promoting sustainable 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:55 p.m.