Triple
T1076048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States federal farm programs |
E23841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agricultural policy program |
C419
|
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: agricultural policy program Context triple: [United States federal farm programs, instanceOf, agricultural policy program]
-
A.
domestic policy program
chosen
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
-
B.
agricultural movement
An agricultural movement is a collective effort or organized campaign aimed at transforming farming practices, land use, or rural livelihoods to achieve social, economic, or environmental goals.
-
C.
agricultural crisis
An agricultural crisis is a severe disruption in farming systems and food production, typically caused by factors such as extreme weather, pests, disease, market shocks, or policy failures, leading to widespread economic hardship and food insecurity.
-
D.
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.
-
E.
economic aid program
An economic aid program is an organized initiative, typically funded by governments or international institutions, designed to provide financial resources, technical assistance, or policy support to stimulate economic development, stabilize economies, or alleviate poverty in targeted regions or populations.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.