Triple

T9807474
Position Surface form Disambiguated ID Type / Status
Subject Oregon ABLE Savings Plan E238187 entity
Predicate accountOwner P347 FINISHED
Object eligible individual with a disability — 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: eligible individual with a disability | Statement: [Oregon ABLE Savings Plan, accountOwner, eligible individual with a disability]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accountOwner
Context triple: [Oregon ABLE Savings Plan, accountOwner, eligible individual with a disability]
  • A. beneficialOwner
    Indicates that one entity is the ultimate beneficiary of ownership rights or economic interest in another entity or asset, even if the ownership is held indirectly or through intermediaries.
  • B. targetOwner
    Indicates that one entity is the owner or primary possessor of a specified target entity.
  • C. primaryOwner
    Indicates that one entity is the main or principal owner of another entity, having the highest level of ownership or control among all possible owners.
  • D. ownedBy chosen
    Indicates that one entity possesses legal or rightful ownership of another entity.
  • E. partOwner
    Indicates that one entity holds a partial or shared ownership stake in another entity.
  • 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_69ca84defac48190abc1148804f184c1 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdab7ddaac8190a5584a5c863fbaa3 completed April 1, 2026, 11:34 p.m.
PD Predicate disambiguation batch_69cd03dd2da881909052fbf29736a773 completed April 1, 2026, 11:39 a.m.
Created at: March 30, 2026, 8:29 p.m.