Triple
T9582390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Revolution of 1848 |
E231204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in 1848 |
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: event in 1848 Context triple: [Austrian Revolution of 1848, instanceOf, event in 1848]
-
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.
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.
-
C.
event in the Greek War of Independence
An event in the Greek War of Independence is a significant historical occurrence between 1821 and 1830 that influenced the course, outcome, or broader context of the Greek struggle to gain independence from the Ottoman Empire.
-
D.
event of the Second International
An event of the Second International is a historically situated gathering, congress, or activity organized under the auspices of the Second International to coordinate, debate, or promote socialist and labor movements across national boundaries.
-
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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:05 p.m.