Triple
T36007739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne green corridor network |
E1041317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecological corridor network |
C10628
|
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: ecological corridor network Context triple: [Melbourne green corridor network, instanceOf, ecological corridor network]
-
A.
ecological corridor
An ecological corridor is a natural or restored habitat pathway that connects separate wildlife populations, enabling species movement, gene flow, and ecosystem resilience across fragmented landscapes.
-
B.
habitat network
chosen
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.
-
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.
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.
-
E.
habitat mosaic
A habitat mosaic is a landscape composed of a patchwork of different habitat types whose spatial arrangement and interactions shape the distribution, movement, and dynamics of species.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.