Triple
T26658646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury Offset Program |
E666579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government payment offset system |
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: government payment offset system Context triple: [Treasury Offset Program, instanceOf, government payment offset system]
-
A.
U.S. Treasury debt collection program
chosen
A U.S. Treasury debt collection program is a federal initiative that centralizes and enforces the collection of delinquent debts owed to government agencies through tools such as offsets, payment arrangements, and legal actions.
-
B.
improper payment prevention system
An improper payment prevention system is a solution that detects, blocks, and mitigates erroneous, fraudulent, or non-compliant payments before or shortly after they are executed.
-
C.
fare payment system
A fare payment system is a coordinated set of processes and technologies that calculates, collects, and validates payments for transportation services from passengers.
-
D.
electronic payment system
An electronic payment system is a digital infrastructure that enables the secure transfer of funds between parties via electronic devices and networks without the need for physical cash or paper-based instruments.
-
E.
government pay scale system
A government pay scale system is a structured framework that defines standardized salary levels, grades, and progression rules for public sector employees based on factors such as role, seniority, qualifications, and performance.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:36 a.m.