Triple
T26658673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasury Offset Program |
E666579
|
entity |
| Predicate | debtTypes |
P116335
|
FINISHED |
| Object | state income tax debts |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: state income tax debts | Statement: [Treasury Offset Program, debtTypes, state income tax debts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debtTypes Context triple: [Treasury Offset Program, debtTypes, state income tax debts]
-
A.
typeOfDebtManaged
chosen
Indicates the specific category or kind of debt that is being handled or overseen in the described relationship or context.
-
B.
debt
Indicates that one entity owes money or an obligation to another entity, typically to be repaid under agreed conditions.
-
C.
loanType
Indicates the specific category or kind of loan associated with an entity or transaction.
-
D.
typicalDebtors
Indicates that one entity is typically or commonly a debtor to another entity, reflecting a usual debtor relationship between them.
-
E.
bankruptcyType
Indicates the specific legal category or chapter under which a bankruptcy case is filed or classified.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:36 a.m.