Triple
T25028245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exchange Stabilization Fund |
E626768
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Treasury fund |
C1633
|
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: U.S. Treasury fund Context triple: [Exchange Stabilization Fund, instanceOf, U.S. Treasury fund]
-
A.
U.S. Treasury security
A U.S. Treasury security is a debt instrument issued by the U.S. Department of the Treasury to finance government operations, backed by the full faith and credit of the United States.
-
B.
federal trust fund
chosen
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.
-
C.
United States foreign assistance account
A United States foreign assistance account is a budgetary category through which the U.S. government allocates and tracks funds dedicated to economic, development, humanitarian, and security assistance to foreign countries and international organizations.
-
D.
United States Sub-Treasury
A United States Sub-Treasury was a regional branch of the federal Treasury Department that held and disbursed government funds, managed public debt transactions, and facilitated financial operations in major cities before the establishment of the Federal Reserve System.
-
E.
state treasury
A state treasury is a government institution responsible for managing a state's financial resources, including revenue collection, budgeting, debt issuance, and investment of public funds.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:07 a.m.