Triple
T13386154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woburn toxic waste contamination cases |
E319450
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water pollution case |
C13531
|
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: water pollution case Context triple: [Woburn toxic waste contamination cases, instanceOf, water pollution case]
-
A.
water contamination incident
A water contamination incident is an event in which a water supply becomes polluted by biological, chemical, or physical agents, posing potential risks to human health and the environment.
-
B.
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.
-
C.
water pollution control law
Water pollution control law is a body of legal rules and regulations designed to prevent, reduce, and remediate contamination of water resources by setting standards, permitting discharges, and enforcing compliance to protect human health and the environment.
-
D.
environmental law case
chosen
An environmental law case is a legal dispute or proceeding that involves the interpretation, application, or enforcement of laws and regulations designed to protect the environment and natural resources.
-
E.
water conference
A water conference is a formal gathering of experts, policymakers, stakeholders, and practitioners focused on discussing, planning, and collaborating around water-related issues such as resource management, sustainability, technology, and policy.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:33 p.m.