Triple
T1965249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dresden uprising of 1849 |
E42672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | revolutionary event in Germany |
C11945
|
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: revolutionary event in Germany Context triple: [Dresden uprising of 1849, instanceOf, revolutionary event in Germany]
-
A.
event in Nazi Germany
An event in Nazi Germany is a historically situated occurrence—political, social, military, cultural, or economic—that took place under the National Socialist regime between 1933 and 1945 and contributed to its policies, ideology, or consequences.
-
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.
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.
-
D.
state of Germany
A state of Germany is a federal constituent entity (Bundesland) with its own government, constitution, and administrative responsibilities within the Federal Republic of Germany.
-
E.
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.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.