Triple
T16153339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philipp Albrecht, Duke of Württemberg |
E391969
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Württemberg |
C37057
|
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: Duke of Württemberg Context triple: [Philipp Albrecht, Duke of Württemberg, instanceOf, Duke of Württemberg]
-
A.
Duke of Bavaria
The Duke of Bavaria is a noble title historically held by the ruler of the Bavarian duchy, signifying high-ranking authority and governance within the region of Bavaria in the Holy Roman Empire and later German territories.
-
B.
King of Württemberg
The King of Württemberg was the hereditary monarch and head of state of the Kingdom of Württemberg, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
-
C.
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.
-
D.
Duke of Saxony
The Duke of Saxony is a high-ranking noble title historically held by rulers of the Saxony region in present-day Germany, signifying territorial authority, military leadership, and political influence within the Holy Roman Empire and later German states.
-
E.
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.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:01 a.m.