Triple
T3633911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Impact Statement |
E77020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental planning document |
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 planning document Context triple: [Environmental Impact Statement, instanceOf, environmental planning document]
-
A.
environmental programme
An environmental programme is an organized set of coordinated activities, policies, and initiatives designed to protect, manage, or improve the natural environment and promote sustainable practices.
-
B.
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.
-
C.
climate policy document
A climate policy document is an official text that outlines goals, strategies, regulations, and implementation plans for mitigating and adapting to climate change within a specific jurisdiction or organization.
-
D.
environmental sustainability goal
An environmental sustainability goal is a specific, measurable objective aimed at preserving or improving natural ecosystems and resources while minimizing negative human impact on the environment over time.
-
E.
environmental conference
An environmental conference is a formal gathering of stakeholders, experts, policymakers, and the public to discuss, share knowledge, and coordinate actions on environmental issues and sustainability initiatives.
- 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.