Triple
T29320836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California coastal zone |
E743509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coastal management zone |
C54828
|
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: coastal management zone Context triple: [California coastal zone, instanceOf, coastal management zone]
-
A.
coastal zone management program document
A coastal zone management program document is an official, typically government-prepared plan that outlines policies, strategies, and regulations for the sustainable use, protection, and development of coastal areas.
-
B.
coastal management approach
A coastal management approach is a strategic framework of policies, practices, and interventions designed to protect, use, and sustainably develop coastal zones while balancing environmental, economic, and social interests.
-
C.
coastal management law
Coastal management law is the body of legal rules, policies, and regulations that govern the use, protection, and development of coastal zones to balance environmental conservation, economic activities, and community interests.
-
D.
coastal access area
A coastal access area is a designated location along the shoreline that provides the public with safe, legal, and convenient entry to coastal lands and waters for recreation, transportation, or environmental enjoyment.
-
E.
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.
- 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_69f0912502c8819087d9e8398ee991a8 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:23 p.m.