Triple
T12137139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Australian Bight Marine National Park (South Australia) |
E289087
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area of Australia |
C30975
|
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: protected area of Australia Context triple: [Great Australian Bight Marine National Park (South Australia), instanceOf, protected area of Australia]
-
A.
Australian marine park
An Australian marine park is a designated ocean and coastal area managed to conserve marine biodiversity and habitats while allowing compatible sustainable use and recreation.
-
B.
IBRA bioregion
An IBRA bioregion is a geographically distinct area in Australia defined by a unique combination of climate, geology, landform, native vegetation, and species assemblages, used for conservation planning and environmental management.
-
C.
region of Queensland
A region of Queensland is a geographically defined area within the Australian state of Queensland characterized by shared environmental, economic, cultural, or administrative features that distinguish it from other parts of the state.
-
D.
region of Western Australia
A region of Western Australia is a defined geographic area within the state used for administrative, economic, cultural, and planning purposes, often characterized by shared environmental features and community identity.
-
E.
protected area portion
A protected area portion is a spatially defined subset of a larger protected area that is managed or designated for specific conservation, regulatory, or land-use purposes.
- F. None of above. chosen
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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.