Triple
T26104447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Nature Preserves system |
E658497
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | statewide network of protected natural areas |
C29446
|
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: statewide network of protected natural areas Context triple: [Ohio Nature Preserves system, instanceOf, statewide network of protected natural areas]
-
A.
network of protected areas
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
B.
protected natural area system
chosen
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
-
C.
protected area designation in the United States
A protected area designation in the United States is an official legal or administrative status applied to lands and waters to conserve natural, cultural, or recreational resources by regulating their use and development.
-
D.
protected areas database
A protected areas database is a structured repository that stores, organizes, and provides access to information about designated conservation sites, including their locations, legal status, management, and ecological characteristics.
-
E.
habitat network
A habitat network is an interconnected system of natural areas and corridors that facilitates the movement, survival, and genetic exchange of species across a landscape.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 26, 2026, 7:57 p.m.