Triple
T3232989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Augustus William of Prussia |
E67785
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian 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: Prussian prince Context triple: [Prince Augustus William of Prussia, instanceOf, Prussian 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.
Duke of Prussia
The Duke of Prussia was a hereditary noble title held by the rulers of the Duchy of Prussia, originally a fief of the Polish Crown that later became the core territory of the Kingdom of Prussia.
-
C.
King in Prussia
King in Prussia was the royal title used by the Hohenzollern rulers of Brandenburg-Prussia from 1701 to 1772, signifying their kingship over Prussia while remaining nominally subordinate to the Holy Roman Emperor within the empire.
-
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.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:08 p.m.