Triple
T32754637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potemkin mutiny |
E837589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Russian Revolution of 1905 |
C8324
|
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 the Russian Revolution of 1905 Context triple: [Potemkin mutiny, instanceOf, event in the Russian Revolution of 1905]
-
A.
event in the Russian Revolution
chosen
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.
-
B.
event in the Persian Constitutional Revolution
An event in the Persian Constitutional Revolution is a historically significant occurrence between 1905 and 1911 in Iran that influenced the struggle to establish a constitutional government and limit monarchical power.
-
C.
event in the Revolutions of 1848
An event in the Revolutions of 1848 is a specific historical occurrence—such as an uprising, political decision, violent clash, or key reform—directly related to the wave of interconnected revolutionary movements that swept across Europe in 1848.
-
D.
event in the Iranian Revolution
A specific occurrence or incident, bounded in time and place, that significantly influenced the course, dynamics, or outcomes of the Iranian Revolution.
-
E.
event of the Boxer Rebellion
The event of the Boxer Rebellion is a violent anti-foreign, anti-Christian uprising in China at the turn of the 20th century, involving clashes between the Boxer militia, Qing imperial forces, and an international coalition of foreign powers.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:12 a.m.