Triple
T4409097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plug Plot Riots |
E94806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in British history |
C15945
|
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: event in British history Context triple: [Plug Plot Riots, instanceOf, event in British history]
-
A.
event in Irish history
An event in Irish history is a significant occurrence or series of actions within Ireland’s past that influenced its political, social, cultural, or economic development.
-
B.
event in the Norman Conquest of England
An event in the Norman Conquest of England is a specific historical occurrence between 1066 and 1071 that contributed to William of Normandy’s seizure and consolidation of power over England.
-
C.
event in the English Civil War
An event in the English Civil War is a specific historical occurrence—such as a battle, political decision, treaty, or social upheaval—that significantly influenced the course, dynamics, or outcomes of the conflict between Royalist and Parliamentarian forces in mid-17th-century England.
-
D.
history of the United Kingdom
The history of the United Kingdom traces the political, social, economic, and cultural development of England, Scotland, Wales, and Northern Ireland from their early origins through unification, empire, conflict, and modern democracy.
-
E.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
- 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:28 p.m.