Triple
T12609227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Leopold of Anhalt-Köthen |
E301067
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Anhalt-Köthen |
C32224
|
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: prince of Anhalt-Köthen Context triple: [Prince Leopold of Anhalt-Köthen, instanceOf, prince of Anhalt-Köthen]
-
A.
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.
-
B.
Landgrave of Hesse-Kassel
The Landgrave of Hesse-Kassel was the hereditary ruler of the German principality of Hesse-Kassel, holding both territorial authority and noble rank within the Holy Roman Empire and its successor states.
-
C.
Duke of Reichstadt
The Duke of Reichstadt is a noble title historically associated with Napoleon II, the son of Napoleon Bonaparte, symbolizing his status and claims within European aristocracy.
-
D.
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.
-
E.
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.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:11 p.m.