Triple
T1235006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agricultural Revolution in Britain |
E26527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | agricultural revolution |
C6895
|
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 revolution Context triple: [Agricultural Revolution in Britain, instanceOf, agricultural revolution]
-
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.
peasant revolt
A peasant revolt is a collective uprising of rural agricultural workers against established authorities or landowners, typically driven by economic hardship, social injustice, and political oppression.
-
E.
ancient civilization
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.