Triple
T7218980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Reich |
E150208
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German Empire |
C10827
|
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: German Empire Context triple: [Second Reich, instanceOf, German Empire]
-
A.
imperial state of the Holy Roman Empire
An imperial state of the Holy Roman Empire was a semi-autonomous political entity—such as a duchy, principality, city, or ecclesiastical territory—directly subject to the authority of the emperor and the imperial diet rather than to any intermediate lord.
-
B.
constituent state of the German Empire
chosen
A constituent state of the German Empire was one of the semi-autonomous kingdoms, grand duchies, duchies, principalities, free Hanseatic cities, or imperial territories that together formed the federal structure of the German Empire from 1871 to 1918.
-
C.
federal state of Germany
A federal state of Germany is a constituent political entity within the Federal Republic of Germany that possesses its own government, constitution, and legislative powers under the framework of the German federal system.
-
D.
King of Westphalia
The King of Westphalia was the sovereign ruler of the short-lived Kingdom of Westphalia (1807–1813), a Napoleonic client state in central Europe governed primarily by Napoleon’s brother Jérôme Bonaparte.
-
E.
German Emperor
A German Emperor is the sovereign ruler who held the imperial title over the German Empire, symbolizing supreme political and military authority within the unified German state from 1871 to 1918.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:53 p.m.