Triple
T11259448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thrifty Food Plan |
E266523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal program parameter |
C17957
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: federal program parameter Context triple: [Thrifty Food Plan, instanceOf, federal program parameter]
-
A.
federal government program
A federal government program is an organized set of activities, services, or regulations funded and administered by the national government to achieve specific public policy goals.
-
B.
fiscal policy program
A fiscal policy program is a coordinated set of government actions and rules that use taxation, spending, and borrowing to influence economic activity, growth, and stability.
-
C.
federal reimbursement formula
chosen
A federal reimbursement formula is a standardized method used by the federal government to calculate how much money it will repay to states, agencies, or organizations for eligible costs under specific programs or regulations.
-
D.
federal policy implementation
Federal policy implementation is the process by which national laws, regulations, and directives are translated into concrete programs, actions, and outcomes through coordination among government agencies, stakeholders, and enforcement mechanisms.
-
E.
program of a state government agency
A program of a state government agency is an organized set of activities, services, and resources designed and managed by the agency to achieve specific public policy goals or deliver particular benefits to residents within the state.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 8, 2026, 9:31 p.m.