Triple
T10053516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacSharry reform |
E208806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Common Agricultural Policy reform |
C2120
|
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: Common Agricultural Policy reform Context triple: [MacSharry reform, instanceOf, Common Agricultural Policy reform]
-
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.
agrarian reform
Agrarian reform is the deliberate reorganization of agricultural land ownership, tenure, and support systems to improve equity, productivity, and rural livelihoods.
-
C.
agricultural research coordination framework
An agricultural research coordination framework is a structured system that aligns, integrates, and manages research activities, resources, and stakeholders across institutions and sectors to address agricultural challenges efficiently and coherently.
-
D.
European Union policy framework
chosen
The European Union policy framework is the overarching system of treaties, institutions, laws, and coordinated strategies through which EU member states collectively design, implement, and enforce policies across economic, social, environmental, and security domains.
-
E.
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.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:57 p.m.