Triple
T26190580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Augustus II, Elector of Saxony |
E654950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | elector of Saxony |
C51216
|
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: elector of Saxony Context triple: [Frederick Augustus II, Elector of Saxony, instanceOf, elector of Saxony]
-
A.
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.
-
B.
Elector of Hesse
The Elector of Hesse was the sovereign ruler of the Electorate of Hesse, a German principality whose prince held the prestigious rank of elector within the Holy Roman Empire and later maintained this title as a mark of dynastic status.
-
C.
King of Saxony
The King of Saxony is the hereditary monarch who historically ruled the Kingdom of Saxony, holding supreme authority over its government, military, and foreign affairs within the German states.
-
D.
Margrave of Meissen
The Margrave of Meissen was a medieval and early modern noble title denoting the ruler of the Margraviate of Meissen, a key frontier principality of the Holy Roman Empire in what is now eastern Germany.
-
E.
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.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:44 p.m.