Triple
T1314776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Agricultural Policy implementation (pre-Brexit) |
E28076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agricultural policy regime |
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: agricultural policy regime Context triple: [Common Agricultural Policy implementation (pre-Brexit), instanceOf, agricultural policy regime]
-
A.
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.
-
B.
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.
-
C.
agricultural landscape
An agricultural landscape is a rural area shaped by human cultivation and management, featuring fields, pastures, and related infrastructure used for the production of crops and livestock.
-
D.
agricultural expert
An agricultural expert is a professional who applies scientific knowledge and practical experience to optimize crop and livestock production, manage natural resources sustainably, and advise stakeholders on best farming practices.
-
E.
colonial policy
Colonial policy is the set of laws, strategies, and administrative practices through which a colonial power governs, exploits, and manages its colonies and their populations.
- F. None of above. chosen
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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.