Triple
T10593867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Declaration on Environment and Development |
E250059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental law instrument |
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: environmental law instrument Context triple: [Rio Declaration on Environment and Development, instanceOf, environmental law instrument]
-
A.
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.
-
B.
environmental impact assessment law
Environmental impact assessment law is the body of legal rules and procedures that requires proposed projects or policies to be evaluated for their potential environmental effects before approval or implementation.
-
C.
environmental law case
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.
-
D.
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.
-
E.
environmental regulation compilation
A curated collection of laws, policies, standards, and guidelines that govern human impacts on the environment, organized for reference, analysis, and compliance support.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
Created at: April 6, 2026, 12:40 p.m.