Triple
T32119122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabiani & Lehane |
E820316
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | crisis management consulting firm |
C188
|
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 consulting firm Context triple: [Fabiani & Lehane, instanceOf, crisis management consulting firm]
-
A.
crisis response organization
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.
-
B.
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.
-
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.
consulting organization
chosen
A consulting organization is a professional services entity that provides expert advice, analysis, and solutions to clients to improve their performance, solve specific problems, or achieve strategic objectives.
-
E.
civilian crisis management structure
A civilian crisis management structure is an organized framework of non-military institutions, roles, and procedures designed to coordinate prevention, response, and recovery efforts during emergencies and disasters affecting the public.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:28 a.m.