Triple
T31056621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIR 2004 |
E791414
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental information access regulation |
C3936
|
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 information access regulation Context triple: [EIR 2004, instanceOf, environmental information access regulation]
-
A.
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.
-
B.
freedom of information law
chosen
Freedom of information law is a legal framework that grants the public the right to access records held by government bodies, subject to specific exemptions for privacy, security, and other protected interests.
-
C.
environmental law journal
An environmental law journal is a scholarly periodical that publishes articles, case notes, and commentary analyzing legal issues, policies, and developments related to environmental protection and natural resources.
-
D.
environmental knowledge network
An environmental knowledge network is a connected system of people, organizations, data, and tools that collaboratively collect, share, and apply information about the environment to support understanding, decision-making, and action.
-
E.
environmental governance instrument
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.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9 p.m.