Triple
T7460907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centralized Receivables Service |
E176245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. Treasury debt collection program |
C22263
|
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 debt collection program Context triple: [Centralized Receivables Service, instanceOf, U.S. Treasury debt collection program]
-
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.
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.
-
C.
CIA program
A CIA program is an organized, often covert initiative or operation designed and managed by the Central Intelligence Agency to achieve specific intelligence, security, or foreign policy objectives.
-
D.
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.
-
E.
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.
- 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.