Triple
T7461036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. savings notes |
E176248
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government savings security |
C22395
|
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. government savings security Context triple: [U.S. savings notes, instanceOf, U.S. government savings security]
-
A.
Treasury securities account system
A Treasury securities account system is a platform that records, manages, and processes the issuance, ownership, transactions, and servicing (e.g., interest and principal payments) of government debt instruments for investors and institutions.
-
B.
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.
-
C.
national security system
A national security system is an integrated framework of institutions, policies, technologies, and processes designed to protect a nation’s sovereignty, citizens, critical infrastructure, and interests from internal and external threats.
-
D.
reserve currency
A reserve currency is a widely trusted national currency that governments and institutions hold in large quantities for international trade, financial stability, and backing their own domestic currencies.
-
E.
Diplomatic Security Service program
A Diplomatic Security Service program is an organized set of policies, resources, and operations designed to protect diplomatic personnel, facilities, and information while supporting secure international engagement.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:38 p.m.