Triple
T26658695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Claims Collection Standards |
E666580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | debt collection standard |
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: debt collection standard Context triple: [Federal Claims Collection Standards, instanceOf, debt collection standard]
-
A.
legal collection
A legal collection is an organized set of legal materials—such as statutes, case law, regulations, and commentary—grouped and maintained for reference, research, or enforcement purposes.
-
B.
collateral standard
A collateral standard is a set of rules and criteria that determine the acceptability, valuation, and risk treatment of assets pledged as security for financial obligations.
-
C.
public debt management office
A public debt management office is a government entity responsible for planning, executing, and monitoring the issuance and servicing of public debt to meet the state's financing needs at the lowest possible cost and acceptable risk.
-
D.
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.
-
E.
intellectual property collection
An intellectual property collection is an organized set of legally protected creations—such as patents, trademarks, copyrights, and trade secrets—managed together as a unified asset portfolio.
- 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.