Triple
T357070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian currency crisis of 1999 |
E7567
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | economic 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: economic event Context triple: [Brazilian currency crisis of 1999, instanceOf, economic event]
-
A.
economic aid program
An economic aid program is an organized initiative, typically funded by governments or international institutions, designed to provide financial resources, technical assistance, or policy support to stimulate economic development, stabilize economies, or alleviate poverty in targeted regions or populations.
-
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.
political event
A political event is a planned or spontaneous occurrence involving political actors, institutions, or the public that aims to influence, express, or respond to political power, policy, or public opinion.
-
D.
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.
-
E.
future event
A future event is an occurrence or happening that has not yet taken place but is anticipated or predicted to occur at a later time.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.