Triple
T25789891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Payment Scheme |
E649520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agricultural subsidy system |
C45774
|
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 subsidy system Context triple: [Single Payment Scheme, instanceOf, agricultural subsidy system]
-
A.
agricultural policy regime
An agricultural policy regime is the structured set of laws, institutions, incentives, and practices through which a government shapes agricultural production, markets, land use, and rural livelihoods over time.
-
B.
agricultural fund
An agricultural fund is an investment vehicle that pools capital to invest in agriculture-related assets such as farmland, agribusiness companies, commodities, or agricultural infrastructure to generate returns linked to the agricultural sector.
-
C.
farming system
A farming system is an integrated set of agricultural practices, resources, and management decisions organized to produce crops and/or livestock within a specific environmental, economic, and social context.
-
D.
agricultural policy initiative
chosen
An agricultural policy initiative is a coordinated set of government or institutional actions designed to influence farming practices, rural development, and food systems to achieve economic, environmental, and social objectives.
-
E.
farmer support program
A farmer support program is an organized initiative that provides agricultural producers with resources, training, financial assistance, and advisory services to improve productivity, sustainability, and livelihoods.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:58 a.m.