Triple
T4094563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Federal Environmental Foundation |
E87782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental foundation |
C13655
|
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 foundation Context triple: [German Federal Environmental Foundation, instanceOf, environmental foundation]
-
A.
environmental partnership
An environmental partnership is a collaborative relationship between organizations, communities, or stakeholders formed to jointly plan and implement actions that protect, restore, or sustainably manage natural resources and ecosystems.
-
B.
environmental organisation
chosen
An environmental organisation is a group dedicated to protecting, preserving, and improving the natural environment through advocacy, conservation, education, and policy influence.
-
C.
environmental cleanup fund
An environmental cleanup fund is a dedicated pool of financial resources established to pay for the assessment, remediation, and long-term management of contaminated sites and environmental damage.
-
D.
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.
-
E.
environmental protection unit
An environmental protection unit is an organized group or division dedicated to monitoring, preserving, and improving the natural environment by enforcing regulations, mitigating pollution, and promoting sustainable practices.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:40 p.m.