Triple
T11259470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrifty Food Plan |
E266523
|
entity |
| Predicate | 2021RevisionEffect |
P7924
|
FINISHED |
| Object | increased SNAP benefit levels |
—
|
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: increased SNAP benefit levels | Statement: [Thrifty Food Plan, 2021RevisionEffect, increased SNAP benefit levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2021RevisionEffect Context triple: [Thrifty Food Plan, 2021RevisionEffect, increased SNAP benefit levels]
-
A.
revisionOf
Indicates that one entity is a modified or updated version of another earlier entity.
-
B.
reassessment
Indicates that a previously made judgment, evaluation, or decision about something is being reviewed and potentially revised.
-
C.
repealEffect
Indicates that one legal act or decision nullifies, cancels, or removes the force or applicability of another.
-
D.
significantRevisionIn
chosen
Indicates that one entity represents a substantial or important change made within another entity, such as a major update or revision occurring in a larger work or version.
-
E.
periodicallyRevisedAt
Indicates that something is updated or revised at recurring, regular points in time.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e936cb048190b4d6fb2851ef8932 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.