Triple
T35927286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bureau of Recovery and Mitigation |
E1039059
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | disaster recovery organization |
C15106
|
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 organization Context triple: [Bureau of Recovery and Mitigation, instanceOf, disaster recovery organization]
-
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.
crisis response organization
chosen
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
-
C.
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.
-
D.
Supporting Organization
A Supporting Organization is an entity that exists primarily to provide resources, services, or assistance to another organization in order to help it achieve its goals.
-
E.
disaster preparedness specialist
A disaster preparedness specialist plans, coordinates, and implements strategies, training, and resources to help communities, organizations, or governments effectively anticipate, withstand, and recover from emergencies and catastrophic events.
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.