Triple
T18303915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penobscot River Restoration Project |
E438433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative conservation effort |
C2976
|
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: collaborative conservation effort Context triple: [Penobscot River Restoration Project, instanceOf, collaborative conservation effort]
-
A.
biodiversity conservation initiative
chosen
A biodiversity conservation initiative is a coordinated effort or program designed to protect, restore, and sustainably manage the variety of life in ecosystems, species, and genetic resources within a defined area or context.
-
B.
global conservation initiative
A global conservation initiative is a coordinated, international effort that unites governments, organizations, and communities to protect biodiversity, restore ecosystems, and promote sustainable use of natural resources worldwide.
-
C.
conservation fund
A conservation fund is a financial mechanism that pools and manages capital to support the long-term protection, restoration, and sustainable use of natural resources and biodiversity.
-
D.
conservation center
A conservation center is a facility dedicated to protecting, studying, and restoring wildlife, habitats, and natural resources through research, education, and hands-on management.
-
E.
area-based conservation measure
An area-based conservation measure is a geographically defined space managed through legal or other effective means to achieve long-term conservation of nature and associated ecosystem services and cultural values.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:35 a.m.