Triple
T6984751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Comprehensive Emergency Management Plan |
E161933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state emergency management plan |
C20646
|
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: state emergency management plan Context triple: [New York State Comprehensive Emergency Management Plan, instanceOf, state emergency management plan]
-
A.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
B.
state policy
A state policy is a formal set of principles and rules adopted by a government to guide decisions and actions in specific public domains such as health, education, economy, or security.
-
C.
emergency management agency
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
D.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
E.
regional planning program
A regional planning program is an organized framework of policies, strategies, and actions designed to guide the coordinated development, land use, infrastructure, and resource management of a specific geographic area over time.
- 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_69c68855dc0481909b4c7e9e9ed273db |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:31 p.m.