Triple

T37310592
Position Surface form Disambiguated ID Type / Status
Subject Missouri ABLE savings program E926194 entity
Predicate hasAnnualContributionLimit P111822 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: [Missouri ABLE savings program, hasAnnualContributionLimit, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAnnualContributionLimit
Context triple: [Missouri ABLE savings program, hasAnnualContributionLimit, yes]
  • A. subjectToAnnualCap chosen
    Indicates that the related amount, usage, or activity is limited by a maximum allowable value that applies on an annual basis.
  • B. hasMaximumBalanceLimit
    Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
  • C. contributionLimitVariesBy
    Indicates that the maximum allowable contribution amount differs depending on a specified factor, such as context, participant, or conditions.
  • D. incomeLimit
    Indicates a specified maximum income threshold that must not be exceeded for a condition, eligibility, or rule to apply.
  • E. designedForMaximumAnnualTransfer
    Indicates that something is intended or optimized to handle the highest possible amount of transfer within a one-year period.
  • 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_69f76eb1bc508190924e9fa5d8acdeb3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd6a1c1c4881908090053bc359b181 completed May 8, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69fd696f24d8819091033afacbdaadc5 completed May 8, 2026, 4:41 a.m.
Created at: May 3, 2026, 4:16 p.m.