Ontology field guide
By NOSIBLE Research
NOSIBLE Event Ontology
The NOSIBLE Event Ontology tracks how one corporate shock becomes operational, customer, legal, governance and financial events.
Corporate shocks propagate through distinct events. A software failure causes disruption. Remediation triggers customer actions. Losses bring claims and litigation. Management responses create governance, disclosure and earnings events. One topic label cannot preserve that sequence.[1]
The NOSIBLE Event Ontology maps reporting into 17 categories, 69 subcategories and 330 event types. World applies those paths to canonical event clusters with point-in-time dates and source coverage. Researchers can construct event chains, separate the initial shock from later consequences and test which stages affect exposed assets across the corporate resolution sequence through time.[2][3]
- Categories
- 416 categories
- Structure
- 3 levels
- World events labelled
- 29.8%
- Stable codes
- Since v1
- Release data
- CC0
Foundations
The NOSIBLE Event Ontology separates corporate shocks from their downstream consequences
The ontology is designed around investable corporate events. Categories separate operational, legal, regulatory, governance, earnings, capital-market, credit, reputation and competitive effects. Subcategories narrow the mechanism. Concrete event types specify the reported action or outcome. The hierarchy supports both broad samples and precise event studies across linked corporate event chains and market regimes.
World classifies what a canonical event record reports. It does not prove causality, materiality or legal liability. A cascade can contain repeated reporting, parallel consequences and classification errors. Researchers should preserve event time, deduplicate source clusters, audit leaf labels and test whether downstream events add information beyond the initial shock, its immediate coverage and concurrent market conditions.[1]
Categories
Seventeen categories expand into 330 concrete corporate events across three levels
The NOSIBLE Event Ontology contains 416 categories: 17 roots, 69 subcategories and 330 leaf events at maximum depth two. The explorer loads bounded branches and exposes definitions, full paths and World counts. World V1.2 assigns a NOSIBLE path to 4,562,361 of 15,311,040 events, giving 29.8% corpus coverage.
4,562,361 of 15,311,040 World events carry labels from NOSIBLE Event Ontology. Select a category to see its count and both relevant shares.
Business Operations
Business Operations
Definition
Changes to how an organisation operates, including continuity, workforce, production, sales and delivery.
Potential research use
Workforce, production and delivery
- Code
- Business Operations
- Events with label
- 1,126,976
- Share of labelled
- 24.7%
- Share of World
- 7.4%
Events with label is the selected count. Label share divides it by 4,562,361 assigned events; World share divides it by all 15,311,040 events.
Representative World V1.2 events
One strong classified example per available year, with up to ten years shown.
Microsoft Acquires Datazen to Enhance Mobile Business Intelligence Capabilities
Coverage 27Dangote Group Fires 48 Staff Including 36 Expats Amid Recession
Coverage 22Google Glass Enterprise Edition Returns for Factory and Business Use
Coverage 57Huawei Cuts Over 600 US Jobs Following Blacklisting and Sanctions
Coverage 71Kentucky Governor Halts Evictions and Cuts Non-Essential Business Operations
Coverage 104Samsung Skips Galaxy Note 21 Due to Global Chip Shortage Crisis
Coverage 184Ford Suspends Russian Operations Citing Ukraine Invasion Concerns
Coverage 223TikTok Challenges Canadian Order to Shut Down Business Operations
Coverage 193P&G Exits Pakistan Direct Operations, Shifts to Distributor Model
Coverage 46XTrend Lab Builds Future of Connected Business Operations
Coverage 139
Browse categories to compare definitions, World V1.2 statistics and representative classified events.
Example usage 1 of 3
Example Usage: Credit Suisse coverage moves from liquidity crisis toward takeover, governance and resolution
The cohort requires Credit Suisse plus crisis, loss, liquidity, deposit, UBS or rescue language. Normalized coverage rises from 91 to 802 events per million after the 19 March 2023 rescue announcement. The fixed entity and risk filter separates a resolution shock from the changing volume of the wider World corpus.[2][3][4]
Capital Markets rises from 14.7% to 23.7% of ontology-assigned events. Corporate Governance rises from 13.2% to 20.0%, while Technical Analysis falls from 17.6% to 4.8%. FINMA and the Swiss National Bank records confirm the transition from confidence and liquidity stress toward takeover, governance and resolution.[2][5]
The cohort requires Credit Suisse plus crisis, loss, liquidity, deposit, UBS or rescue language. The comparison splits at 19 March 2023. Coverage divides matched events by all World events in each phase. Composition divides by ontology-assigned cohort events. The result describes the resolution sequence; it does not measure loss severity, depositor behaviour, counterparty exposure or causal market impact.
Example usage 2 of 3
Example Usage: Microsoft–Activision moves from antitrust review to layoffs within 100 days of closing
Microsoft–Activision reporting changes event type three times. Antitrust Case Filed and Antitrust Case Updated dominate before the 13 October 2023 close. Merger Concluded peaks at completion. Workforce Reduced appears in late January 2024 and becomes the leading event type during the first restructuring wave roughly 100 days after the deal closes.[8]
Those phases carry different financial questions. Antitrust events change closing probability. Completion starts the ownership and accounting clock. Workforce reductions reveal integration costs and synergy execution. A single acquisition keyword merges all three. Event classifications let researchers align spreads, revisions, operating margins and competitor responses to the mechanism that actually changed during each distinct deal phase.[9]
- Corporate Governance
- +18.9pp
- Business Operations
- +9.9pp
- Legal Actions
- -14.0pp
- Regulatory Compliance
- -16.5pp
The fixed English cohort covers June 2023 through February 2024 and requires Microsoft plus Activision, Blizzard or Call of Duty. Each line pools event-type counts across the current and prior twenty days, then divides by all English World events in that window.
Example usage 3 of 3
Example Usage: CrowdStrike reporting moves from outage disclosure into fraud cases and apologies
CrowdStrike reporting changes event type after the 19 July 2024 outage. Cyber-attack and software-vulnerability classifications peak during the acute response. Fraud Case Filed appears in the following weeks, while Apology Statement Issued arrives later. The line chart exposes the sequence that pooled before-and-after shares conceal.[6]
Each phase starts a new risk clock. The outage affects clients, vendors and operations at once. Fraud cases and apologies shift attention to legal, insurance, churn and trust costs. Researchers can test prices, sales and client events by phase instead of pooling all CrowdStrike news into one risk signal.[7]
- Legal Actions
- +24.4pp
- Reputational Risk
- -46.4pp
- Business Operations
- +12.2pp
- Normalized coverage
- -994 per million
The explicit English CrowdStrike-outage cohort covers July through October 2024. Each line pools NOSIBLE event-type counts across the current and prior thirteen days, then divides by all English World events in that window. The chart describes the reporting sequence, not realized losses.
Data and sources
Download NOSIBLE Events and References
Downloads
Download categories and counts as CSV, or the complete machine-readable release as JSON.
Release details and citation files
ManifestRelease READMECC0 license and scopeCitation fileChangelog
Need the complete World event schema? Open the World data dictionary.
References
- [1]Cummins, J. D., Lewis, C. M., & Wei, R. (2006). The market value impact of operational loss events for US banks and insurers. Journal of Banking & Finance, 30(10), 2605-2634.
- [2]Swiss Financial Market Supervisory Authority. (2023). FINMA approves merger of UBS and Credit Suisse.
- [3]Swiss National Bank. (2023). Swiss National Bank provides substantial liquidity assistance to support UBS takeover of Credit Suisse.
- [4]Swiss Federal Council. (2023). Safeguarding financial market stability: Federal Council welcomes and supports UBS takeover of Credit Suisse.
- [5]UBS Group AG. (2023). UBS completes Credit Suisse acquisition.
- [8]U.S. Federal Trade Commission. Microsoft/Activision Blizzard matter, docket 9412.
- [9]Microsoft. (2023). Welcoming the teams at Activision Blizzard King to Xbox.
- [6]CrowdStrike. (2024). Preliminary post-incident review: Falcon content configuration update.
- [7]CrowdStrike Holdings, Inc. (2025). Form 10-K for the year ended January 31, 2025.
Continue exploring