Triple
T37310542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Missouri 529 education savings programs |
E926193
|
entity |
| Predicate | savingsGoal |
P14665
|
FINISHED |
| Object | reduce future student loan debt |
—
|
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: reduce future student loan debt | Statement: [Missouri 529 education savings programs, savingsGoal, reduce future student loan debt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: savingsGoal Context triple: [Missouri 529 education savings programs, savingsGoal, reduce future student loan debt]
-
A.
economicGoal
chosen
Indicates that an entity has a targeted economic outcome or objective it aims to achieve.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
goalValue
Indicates the target or desired value that an entity aims to achieve or reach.
-
D.
budgetTarget
Indicates that a specific financial goal or spending limit has been set for a given entity, period, or activity.
-
E.
stabilityGoal
Indicates a relationship where an action, policy, or entity is aimed at achieving, maintaining, or enhancing stability in a given system or context.
- 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_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.