Triple
T23229472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wilhelm Victor August Ernst |
E581110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Crown Prince of the German Empire |
C47416
|
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: Crown Prince of the German Empire Context triple: [Friedrich Wilhelm Victor August Ernst, instanceOf, Crown Prince of the German Empire]
-
A.
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.
-
B.
Chancellor of the German Empire
The Chancellor of the German Empire was the head of government and chief executive officer of the empire, responsible for directing imperial policy and administration under the authority of the German Emperor from 1871 to 1918.
-
C.
former German prince
A former German prince is an individual who once held, but no longer possesses, a princely title within the historical German nobility, typically due to political, legal, or dynastic changes.
-
D.
anti-king of Germany
An anti-king of Germany was a rival claimant elected by a faction of princes in opposition to a reigning or officially recognized German king or Holy Roman Emperor, typically during periods of dynastic or political conflict.
-
E.
prince of the Holy Roman Empire
A prince of the Holy Roman Empire was a secular or ecclesiastical ruler who held immediate authority under the emperor, possessing territorial sovereignty and a vote in the Imperial Diet.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:09 p.m.