Triple
T1534623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 101-380 |
E32522
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | oil pollution law |
C6666
|
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: oil pollution law Context triple: [Public Law 101-380, instanceOf, oil pollution law]
-
A.
water pollution control law
chosen
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.
-
B.
waste management law
Waste management law is the body of legal rules and regulations governing the generation, collection, transport, treatment, recycling, and disposal of waste to protect human health and the environment.
-
C.
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.
-
D.
law of the sea institution
A law of the sea institution is an organization or body responsible for developing, interpreting, implementing, or enforcing legal rules and frameworks governing the use, management, and protection of the world’s oceans and marine resources.
-
E.
conservation law
A conservation law is a fundamental principle stating that a specific measurable quantity of an isolated physical system remains constant over time despite internal changes or interactions.
- 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_69a885ea86308190998f6bc14bb91f8e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:26 p.m.