Triple
T4976554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crisis Response Center |
E111778
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crisis management unit |
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: crisis management unit Context triple: [Crisis Response Center, instanceOf, crisis management unit]
-
A.
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.
-
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.
crisis-management mandate
A crisis-management mandate is a formal directive that defines the authority, responsibilities, and procedures an organization must follow to prepare for, respond to, and recover from critical incidents or emergencies.
-
D.
civil affairs unit
A civil affairs unit is a military organization responsible for managing relationships and coordination between armed forces and civilian populations, authorities, and institutions in areas of operation.
-
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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:33 p.m.