Triple
T7460931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centralized Receivables Service |
E176245
|
entity |
| Predicate | debtTypeExcluded |
P34541
|
FINISHED |
| Object | federal tax debt |
—
|
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: federal tax debt | Statement: [Centralized Receivables Service, debtTypeExcluded, federal tax debt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: debtTypeExcluded Context triple: [Centralized Receivables Service, debtTypeExcluded, federal tax debt]
-
A.
debt
Indicates that one entity owes money or an obligation to another entity, typically to be repaid under agreed conditions.
-
B.
excludedFrom
chosen
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
exemptionType
Indicates the specific category or kind of exemption that applies in a given context.
-
D.
exemptedFrom
Indicates that an entity is not subject to, or is formally released from, a rule, obligation, requirement, or liability that would otherwise apply.
-
E.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d525708190b7838e07ac2fbe1f |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:38 p.m.