Triple
T23265410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reclamation Fund |
E588132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolving fund |
C47444
|
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: revolving fund Context triple: [Reclamation Fund, instanceOf, revolving fund]
-
A.
state revolving fund
A state revolving fund is a pool of capital, typically capitalized by federal and state contributions, that provides low-interest loans for eligible public infrastructure projects and is replenished as borrowers repay, allowing continuous reinvestment in similar projects.
-
B.
stabilization fund
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.
rural development fund
A rural development fund is a financial mechanism that pools and allocates resources to support economic growth, infrastructure, and social services in rural areas, aiming to reduce regional disparities and improve quality of life.
-
D.
regional development fund
A regional development fund is a financial mechanism that pools and allocates resources to support economic growth, infrastructure, and social development projects within a specific geographic area.
-
E.
planned regional monetary fund
A planned regional monetary fund is a proposed financial institution designed to pool resources from member countries within a specific region to provide monetary stability, balance-of-payments support, and coordinated economic policies.
- F. None of above. chosen
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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 4:34 p.m.