Triple
T33759310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Coastal Management Program |
E865064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coastal management program |
C60681
|
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 program Context triple: [Illinois Coastal Management Program, instanceOf, coastal management program]
-
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 research program
A coastal research program is an organized, often interdisciplinary initiative that systematically studies coastal environments, processes, and communities to inform sustainable management, policy, and adaptation to environmental change.
-
D.
coastal management zone
A coastal management zone is a designated area along the shoreline where policies and practices are coordinated to balance environmental protection, economic use, and community safety.
-
E.
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.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.