Triple
T21468125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tañon Strait Protected Seascape |
E529647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected seascape |
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: protected seascape Context triple: [Tañon Strait Protected Seascape, instanceOf, protected seascape]
-
A.
protected landscape area
A protected landscape area is a designated region where the interaction of people and nature over time has produced a distinct character with significant ecological, cultural, and scenic value that is conserved and managed through legal or other effective means.
-
B.
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.
-
C.
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.
-
D.
coastal reservation
A coastal reservation is a protected shoreline area designated to conserve marine and coastal ecosystems while allowing limited, sustainable human use and cultural activities.
-
E.
public shoreline
A public shoreline is a coastal area legally accessible to all people for recreation, passage, and enjoyment, typically protected by regulations that prevent exclusive private ownership or obstruction.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:15 p.m.