Triple
T22077450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contingency Fund of India |
E545557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government contingency fund |
C21079
|
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: government contingency fund Context triple: [Contingency Fund of India, instanceOf, government contingency fund]
-
A.
government budget
A government budget is a financial plan that outlines a government's projected revenues and expenditures over a specific period, typically one fiscal year, to achieve its economic and policy objectives.
-
B.
stabilization fund
chosen
A stabilization fund is a reserve of financial resources established by a government or organization to smooth out economic fluctuations, stabilize revenues or prices, and provide a buffer against external shocks.
-
C.
federal trust fund
A federal trust fund is a government account that collects specific revenues and uses them for designated purposes, often outside the general budget, according to law.
-
D.
U.S. government savings security
A U.S. government savings security is a low-risk, interest-bearing financial instrument issued by the U.S. Treasury that allows individuals to lend money to the federal government in exchange for guaranteed returns over time.
-
E.
continuity of government framework
A continuity of government framework is a structured set of policies, plans, and procedures designed to ensure that essential governmental functions and leadership can continue or be rapidly restored during and after emergencies or disruptions.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.