Triple
T384086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Inflation |
E8741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical inflation episode |
C138
|
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: historical inflation episode Context triple: [Great Inflation, instanceOf, historical inflation episode]
-
A.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
B.
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.
-
C.
era in United States history
An era in United States history is a distinct time period characterized by particular political, social, economic, and cultural conditions or transformative events that differentiate it from other periods.
-
D.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
E.
financial crisis
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.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.