Triple
T34869113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cross River rainforest landscape |
E1005099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transboundary ecoregion |
C31232
|
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: transboundary ecoregion Context triple: [Cross River rainforest landscape, instanceOf, transboundary ecoregion]
-
A.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
-
B.
transboundary river system
A transboundary river system is a network of rivers and related water bodies that cross or form political borders between two or more countries, requiring shared management and governance.
-
C.
ecotone
An ecotone is a transitional zone between two distinct ecological communities where species from both habitats interact and biodiversity is often heightened.
-
D.
ecozone
An ecozone is a large geographic area defined by its distinct assemblage of plant and animal species, climate, and ecological history, representing a major division of the Earth's biosphere.
-
E.
ecoregion complex
chosen
An ecoregion complex is a broad geographic area composed of multiple adjacent or closely related ecoregions that share similar environmental conditions, ecological processes, and characteristic species assemblages.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.