Triple
T17076282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prague Slavic Congress of 1848 |
E414355
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 1848 Revolution event |
C11944
|
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: 1848 Revolution event Context triple: [Prague Slavic Congress of 1848, instanceOf, 1848 Revolution event]
-
A.
event in the Revolutions of 1848
chosen
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.
-
B.
wave of revolutions
A wave of revolutions is a historically clustered series of uprisings or regime changes that spread across multiple countries or regions within a relatively short period, often driven by shared grievances, ideas, or triggering events.
-
C.
revolutionary event in Germany
A revolutionary event in Germany is a significant, often abrupt socio-political upheaval within German territory that challenges or overturns existing power structures, institutions, or social orders.
-
D.
workers' revolt
A workers' revolt is a collective uprising by laborers against perceived exploitation or unjust working conditions, aiming to challenge or overturn existing power and economic structures.
-
E.
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.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.