Triple
T26328867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Waterfront Revitalization and Coastal Resources Act |
E662329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coastal management law |
C51424
|
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 law Context triple: [New York State Waterfront Revitalization and Coastal Resources Act, instanceOf, coastal management law]
-
A.
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.
-
B.
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.
-
C.
coastal engagement
Coastal engagement is the dynamic interaction between people and coastal environments through social, economic, cultural, and ecological activities that shape and are shaped by shoreline spaces.
-
D.
coastal passage
A coastal passage is a navigable route that follows along a shoreline, often using natural channels and sheltered waters between the coast and offshore features such as islands or reefs.
-
E.
disaster management law
Disaster management law is the body of legal rules, principles, and procedures that governs how governments and organizations prepare for, respond to, recover from, and mitigate natural or human-made disasters while protecting public safety and rights.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:32 p.m.