Triple
T6683026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Revolution of 1918–1919 |
E152033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in German history |
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: event in German history Context triple: [German Revolution of 1918–1919, instanceOf, event in German history]
-
A.
revolutionary event in Germany
chosen
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.
-
B.
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.
-
C.
event in British history
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
-
D.
event in Serbian history
A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
-
E.
event in the Franco-Prussian War
A specific occurrence or series of actions during the Franco-Prussian War that involved identifiable participants, took place at a particular time and location, and had notable military, political, or social consequences.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:04 p.m.