Triple
T20184773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sigismund |
E492825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hohenzollern prince |
C12507
|
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: Hohenzollern prince Context triple: [John Sigismund, instanceOf, Hohenzollern prince]
-
A.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
B.
Prussian prince
chosen
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
-
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.
Grand Duke of Hesse
The Grand Duke of Hesse was the hereditary sovereign ruler of the Grand Duchy of Hesse, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
-
E.
Grand Duke of Mecklenburg-Schwerin
The Grand Duke of Mecklenburg-Schwerin was the hereditary sovereign ruler of the Grand Duchy of Mecklenburg-Schwerin, a German state within the Holy Roman Empire and later the German Confederation and German Empire, until the monarchy’s abolition in 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:36 p.m.