Triple
T27152350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skomer Marine Conservation Zone |
E682423
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marine conservation zone |
C15937
|
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: marine conservation zone Context triple: [Skomer Marine Conservation Zone, instanceOf, marine conservation zone]
-
A.
marine conservation area
chosen
A marine conservation area is a designated ocean or coastal region managed to protect marine ecosystems, species, and natural resources from harmful human activities while allowing compatible, sustainable use.
-
B.
marine conservation center
A marine conservation center is a facility dedicated to protecting ocean ecosystems through research, education, wildlife rehabilitation, and community engagement.
-
C.
state marine reserve
A state marine reserve is a designated ocean or coastal area managed by a state government where the extraction or disturbance of natural marine resources is highly restricted or prohibited to protect ecosystems and biodiversity.
-
D.
marine park area
A marine park area is a designated ocean or coastal zone managed to conserve marine ecosystems and biodiversity while allowing regulated recreation, education, and sometimes sustainable use.
-
E.
ecologically significant marine area
An ecologically significant marine area is a distinct ocean or coastal region that contains unique, rare, or highly productive habitats and species, providing critical ecological functions and contributing disproportionately to marine biodiversity and ecosystem health.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:14 a.m.