Triple
T17005063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roth IRA |
E412548
|
entity |
| Predicate | allowsCatchUpContributions |
P126140
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Roth IRA, allowsCatchUpContributions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsCatchUpContributions Context triple: [Roth IRA, allowsCatchUpContributions, yes]
-
A.
alsoEligible
Indicates that an entity qualifies for an additional option, status, or benefit beyond its primary or initial eligibility.
-
B.
mayAlsoCredit
Indicates that an additional party can optionally be acknowledged or given credit in relation to the same work, contribution, or transaction.
-
C.
mayProvideEligibilityFor
Indicates that one entity can serve as a basis or qualifying factor that makes another entity eligible for something (such as a benefit, status, or action).
-
D.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
E.
allowsAnnualHHSReportingWhen
Indicates the conditions under which annual reporting to the U.S. Department of Health and Human Services (HHS) is permitted or enabled.
- F. None of above. chosen
Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d382400c819092ec0ca0de815888 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.