Triple
T37249027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reichsreform von Worms 1495 |
E923939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ereignis der deutschen Geschichte |
C27133
|
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: Ereignis der deutschen Geschichte Context triple: [Reichsreform von Worms 1495, instanceOf, Ereignis der deutschen Geschichte]
-
A.
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.
-
B.
historical period in German politics
A historical period in German politics is a distinct span of time characterized by specific political structures, key events, dominant ideologies, and notable actors that collectively shape the development of Germany’s political landscape.
-
C.
event in Danish history
A significant occurrence or series of actions situated in Denmark’s past that influenced its political, social, cultural, or economic development.
-
D.
historic event
chosen
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
E.
Rechtsgrundlage der deutschen Wiedervereinigung
Die Rechtsgrundlage der deutschen Wiedervereinigung umfasst das Zusammenspiel von innerstaatlichen und völkerrechtlichen Normen – insbesondere den Einigungsvertrag, das Grundgesetz (insb. Art. 23 a.F. und Art. 146 GG) sowie den Zwei-plus-Vier-Vertrag – die gemeinsam die staatliche Einheit Deutschlands rechtlich ermöglichten und absicherten.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.