Triple
T4089067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyRA retirement savings initiative |
E87660
|
entity |
| Predicate | maximumAccountBalance |
P29667
|
FINISHED |
| Object | 15000 USD |
—
|
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: 15000 USD | Statement: [MyRA retirement savings initiative, maximumAccountBalance, 15000 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumAccountBalance Context triple: [MyRA retirement savings initiative, maximumAccountBalance, 15000 USD]
-
A.
historicalBalance
Indicates a relationship where an entity’s past or previous balance amount is recorded or referenced over time.
-
B.
maximumLoanAmountUSD
Indicates the highest amount of money, expressed in U.S. dollars, that can be loaned under a given agreement or condition.
-
C.
maximumGrantAmount
Indicates the highest monetary value that can be awarded or granted under a specific grant, program, or agreement.
-
D.
maximumNumber
chosen
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
E.
hasMinimumBalanceForTrain
Indicates that an entity’s balance meets or exceeds the minimum required amount to use or board a train.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.