Triple
T8019610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverado Savings and Loan collapse |
E186705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | savings and loan crisis event |
C361
|
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: savings and loan crisis event Context triple: [Silverado Savings and Loan collapse, instanceOf, savings and loan crisis event]
-
A.
financial crisis
chosen
A financial crisis is a severe disruption in financial markets and institutions characterized by sharp declines in asset prices, loss of confidence, liquidity shortages, and widespread insolvency risks that significantly harm the broader economy.
-
B.
financial crisis intervention
Financial crisis intervention is a coordinated set of strategies and actions designed to stabilize individuals, organizations, or economies facing acute financial distress, mitigate immediate harm, and support recovery toward sustainable financial health.
-
C.
sovereign default event
A sovereign default event is the failure or restructuring by a national government to meet its debt obligations as originally agreed, triggering legal, financial, and market consequences.
-
D.
economic depression
An economic depression is a prolonged, severe downturn in economic activity characterized by significant declines in output, high unemployment, widespread business failures, and persistent financial distress across an economy.
-
E.
macroeconomic event
A macroeconomic event is a significant occurrence or policy change that affects the overall performance, structure, or behavior of an economy at the national or global level.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:20 p.m.