Triple
T38310343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City coastal resilience network |
E1033665
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coastal resilience system |
C38293
|
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 resilience system Context triple: [New York City coastal resilience network, instanceOf, coastal resilience system]
-
A.
coastal park system
A coastal park system is an interconnected network of protected shoreline areas managed to conserve coastal ecosystems while providing public access, recreation, and environmental education.
-
B.
coastal habitat complex
A coastal habitat complex is an interconnected mosaic of shoreline, intertidal, and nearshore ecosystems that function together to support diverse species, ecological processes, and coastal resilience.
-
C.
coastal management program
A coastal management program is an organized framework of policies, practices, and projects designed to protect, restore, and sustainably use coastal environments while balancing ecological, economic, and community needs.
-
D.
coastal management approach
chosen
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.
-
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.
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.