Triple
T20406042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital Readmissions Reduction Program |
E500470
|
entity |
| Predicate | implementedInFiscalYear |
P102202
|
FINISHED |
| Object | FY2013 |
—
|
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: FY2013 | Statement: [Hospital Readmissions Reduction Program, implementedInFiscalYear, FY2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedInFiscalYear Context triple: [Hospital Readmissions Reduction Program, implementedInFiscalYear, FY2013]
-
A.
fiscalYearHonored
Indicates that a particular fiscal year is formally recognized, celebrated, or given special acknowledgment in relation to an entity or event.
-
B.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
C.
hasFiscalYearCoverage
chosen
Indicates that one entity’s applicable period, data, or responsibility spans or corresponds to a specified fiscal year or range of fiscal years.
-
D.
financialYearStart
Indicates the date or point in time when an entity’s financial or fiscal year begins.
-
E.
budgetFiscalYear
Indicates the fiscal year to which a particular budget or budgeting activity applies.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67992cfb88190ae49a1723e6667a1 |
completed | April 20, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.