Triple
T35615143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Office of Recovery and Resiliency |
E1029144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster recovery agency |
C5073
|
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: disaster recovery agency Context triple: [North Carolina Office of Recovery and Resiliency, instanceOf, disaster recovery agency]
-
A.
disaster recovery solution
A disaster recovery solution is a comprehensive system of tools, processes, and policies designed to quickly restore critical IT services and data after disruptive events, minimizing downtime and business impact.
-
B.
emergency management agency
chosen
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.
-
C.
risk management agency
A risk management agency is an organization that identifies, assesses, and mitigates potential threats to an entity’s assets, operations, and objectives through strategic planning, analysis, and control measures.
-
D.
public defender support agency
A public defender support agency is an organization that provides resources, training, policy advocacy, and administrative or specialized legal support to public defenders to enhance the quality and effectiveness of indigent defense services.
-
E.
disaster management initiative
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.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.