Triple
T1619286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decembrist revolt |
E34793
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Russian history |
C5725
|
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 Russian history Context triple: [Decembrist revolt, instanceOf, event in Russian history]
-
A.
turning point in Russian history
chosen
A turning point in Russian history is a pivotal event or period that fundamentally alters the country’s political, social, or economic trajectory, leading to lasting and often irreversible change.
-
B.
event in the Russian Revolution
An event in the Russian Revolution is a significant historical occurrence—such as a protest, decree, battle, or political change—that contributed to the overthrow of the tsarist regime and the subsequent rise of Soviet power.
-
C.
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.
-
D.
event in the dissolution of the Soviet Union
An "event in the dissolution of the Soviet Union" is a historically significant occurrence—political, economic, social, or military—that contributed to or marked a step in the breakup of the USSR into independent states between the mid-1980s and 1991.
-
E.
Polish military history event
A Polish military history event is a significant occurrence involving Poland’s armed forces—such as battles, campaigns, uprisings, operations, or strategic decisions—that influenced the course of Poland’s national or military development.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.