Triple
T17622175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interim Biogeographic Regionalisation for Australia |
E429733
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biogeographic regionalisation framework |
C33781
|
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: biogeographic regionalisation framework Context triple: [Interim Biogeographic Regionalisation for Australia, instanceOf, biogeographic regionalisation framework]
-
A.
biogeography book
A biogeography book is a comprehensive text that explores the distribution of species and ecosystems across geographic space and through geological time, explaining the ecological and evolutionary processes that shape these patterns.
-
B.
ecoregion classification system
chosen
An ecoregion classification system is a structured framework that categorizes geographic areas into distinct ecological regions based on shared environmental conditions, ecosystems, and biodiversity patterns.
-
C.
biosphere region
A biosphere region is a large, distinct area of Earth where living organisms interact with each other and their physical environment, forming an integrated ecological system.
-
D.
floristic region
A floristic region is a geographic area defined by its distinct composition of plant species and vegetation types, reflecting shared evolutionary history and environmental conditions.
-
E.
ecogeographical rule
An ecogeographical rule is a principle that describes consistent patterns in the variation of species’ traits (such as body size, shape, or coloration) along environmental gradients like latitude, altitude, or climate.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:52 a.m.