Triple
T6326654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Assistance programs |
E141878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency management program |
C11471
|
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: emergency management program Context triple: [Public Assistance programs, instanceOf, emergency management program]
-
A.
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.
-
B.
emergency management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
-
C.
disaster management initiative
chosen
A disaster management initiative is a coordinated program or effort designed to prevent, prepare for, respond to, and recover from natural or human-made disasters to protect lives, property, and the environment.
-
D.
crisis management activity
A crisis management activity is a coordinated task or operation undertaken to prepare for, respond to, mitigate, or recover from an unexpected disruptive event that threatens an organization’s objectives or stakeholders.
-
E.
emergency legislation
Emergency legislation is a special category of law enacted rapidly, often with expedited procedures and temporary scope, to address urgent or unforeseen crises requiring immediate governmental action.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.