Triple
T23308190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Louis I, Prince of Anhalt-Dornburg |
E590507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince of Anhalt-Dornburg |
C47497
|
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-Dornburg Context triple: [John Louis I, Prince of Anhalt-Dornburg, instanceOf, Prince of Anhalt-Dornburg]
-
A.
Prince of Nassau-Usingen
The Prince of Nassau-Usingen was the sovereign ruler of the small German principality of Nassau-Usingen within the Holy Roman Empire and later the Confederation of the Rhine.
-
B.
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.
-
C.
Duke of Lauenburg
The Duke of Lauenburg is a noble title historically associated with the ruler of the Duchy of Lauenburg, a small German principality within the Holy Roman Empire and later states of the German Confederation.
-
D.
Duke of Saxe-Weimar
The Duke of Saxe-Weimar was a hereditary noble title held by the ruler of the historical German duchy of Saxe-Weimar within the Holy Roman Empire and later German states.
-
E.
Duke of Holstein
The Duke of Holstein is a noble title historically held by rulers of the duchy of Holstein in northern Germany, often intertwined with the Danish crown and regional power politics in Schleswig-Holstein.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:05 p.m.