Triple
T32733045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farm to Fork Strategy |
E837005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | food systems strategy |
C7382
|
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: food systems strategy Context triple: [Farm to Fork Strategy, instanceOf, food systems strategy]
-
A.
food security initiative
A food security initiative is a coordinated program or policy designed to ensure consistent, reliable access to sufficient, safe, and nutritious food for all people, particularly vulnerable populations.
-
B.
food security platform
A food security platform is a digital system that connects producers, distributors, and consumers to monitor, manage, and ensure reliable access to safe, nutritious, and affordable food.
-
C.
food and agriculture policy conference
A food and agriculture policy conference is a professional gathering where policymakers, researchers, industry stakeholders, and advocates convene to discuss, analyze, and shape policies affecting food systems, farming, rural development, and agricultural sustainability.
-
D.
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.
-
E.
agricultural policy regime
chosen
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.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.