Triple
T31018017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltimore Ecosystem Study |
E790375
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Long Term Ecological Research project |
C25014
|
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: Long Term Ecological Research project Context triple: [Baltimore Ecosystem Study, instanceOf, Long Term Ecological Research project]
-
A.
Long Term Ecological Research site
chosen
A Long Term Ecological Research site is a designated location where scientists conduct sustained, systematic studies of ecological processes and environmental change over extended periods, often decades.
-
B.
long-term ecological study
A long-term ecological study is an extended, systematic investigation of ecosystems or populations over many years or decades to detect gradual changes, long-term trends, and ecological processes that short-term studies might miss.
-
C.
ecological research network
An ecological research network is a collaborative system of researchers, institutions, and data infrastructures that share methods, observations, and analyses to study and understand ecological patterns and processes across scales.
-
D.
ecological research area
An ecological research area is a designated geographic region where scientists systematically study the relationships among organisms, their environments, and ecological processes over time.
-
E.
ecological site
An ecological site is a distinctive kind of land defined by specific climate, soil, and topographic conditions that support a characteristic range of plant communities and ecological processes.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.