Triple
T26318127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GetYourRefund |
E662027
|
entity |
| Predicate | supportedTaxYear |
P130123
|
FINISHED |
| Object | recent tax years in the United States |
—
|
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: recent tax years in the United States | Statement: [GetYourRefund, supportedTaxYear, recent tax years in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedTaxYear Context triple: [GetYourRefund, supportedTaxYear, recent tax years in the United States]
-
A.
supportsYear
chosen
Indicates that one entity is compatible with, or provides functionality for, a specified year or range of years.
-
B.
appliesToTaxYear
Indicates the specific tax year or fiscal period to which a tax-related rule, record, or obligation is applicable.
-
C.
taxSupport
Indicates that one entity provides financial or tax-related assistance, backing, or resources to another entity.
-
D.
introducedInTaxYear
Indicates that something (such as a rule, benefit, or provision) first became applicable or was brought into effect in a specified tax year.
-
E.
notAvailableForTaxYear
Indicates that something cannot be used, claimed, or applied for a specified tax year.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 26, 2026, 10:26 p.m.