Triple
T2218675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | July Days |
E48089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the Russian Revolution |
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 Context triple: [July Days, instanceOf, event in the Russian Revolution]
-
A.
campaign of the Russian Civil War
A campaign of the Russian Civil War is a coordinated series of military operations conducted by opposing factions over a specific region and period, aimed at achieving strategic political and territorial objectives within the broader conflict.
-
B.
event of the French Revolution
An event of the French Revolution is a historically specific occurrence between 1789 and 1799 in France that significantly influenced the revolution’s political, social, or cultural trajectory.
-
C.
episode of the French Revolution
An episode of the French Revolution is a distinct historical event or sequence of actions occurring within the broader revolutionary period, involving specific actors, locations, and political or social developments.
-
D.
event in the Indonesian National Revolution
A historically significant occurrence, such as a battle, political decision, diplomatic action, or social upheaval, that took place between 1945 and 1949 and influenced the course or outcome of the Indonesian National Revolution.
-
E.
turning point in Russian history
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.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:46 p.m.