Triple
T26235008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monarto Conservation Park |
E656140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area of South 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 South Australia Context triple: [Monarto Conservation Park, instanceOf, protected area of South Australia]
-
A.
protected area of Australia
chosen
A protected area of Australia is a legally designated region of land or sea managed to conserve the country’s natural ecosystems, biodiversity, and cultural heritage while often allowing for regulated public use and research.
-
B.
protected area of South Africa
A protected area of South Africa is a legally designated geographic space, such as a national park, nature reserve, or marine protected area, managed to conserve biodiversity, ecosystems, and cultural heritage while often supporting sustainable tourism and local livelihoods.
-
C.
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.
-
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.
subregion of Tasmania
A subregion of Tasmania is a defined geographic or administrative area within the Australian state of Tasmania, characterized by shared environmental, economic, cultural, or planning attributes.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 9:01 p.m.