Triple
T3633863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 91-190 |
E77019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | framework environmental law |
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: framework environmental law Context triple: [Public Law 91-190, instanceOf, framework environmental law]
-
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 law research organization
An environmental law research organization is an entity that conducts legal analysis, policy studies, and advocacy support focused on environmental protection, natural resource management, and sustainability regulations.
-
C.
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.
-
D.
natural resources law
Natural resources law is the body of legal rules and principles governing the ownership, use, management, and conservation of natural resources such as land, water, minerals, forests, and wildlife.
-
E.
international environmental regulation
International environmental regulation is the body of treaties, agreements, and legal frameworks through which nations collectively manage and limit activities that impact the global environment and shared natural resources.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:24 p.m.