Triple
T37338881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elector Palatine Louis V |
E926975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elector Palatine of the Rhine |
C65425
|
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 Palatine of the Rhine Context triple: [Elector Palatine Louis V, instanceOf, Elector Palatine of the Rhine]
-
A.
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.
-
B.
Duke of Württemberg
The Duke of Württemberg was the hereditary sovereign ruler of the Duchy of Württemberg, a historical German territory within the Holy Roman Empire and later the German Confederation.
-
C.
Duke of Jülich
The Duke of Jülich was a high-ranking noble ruler of the historic Duchy of Jülich in the Holy Roman Empire, holding territorial, military, and political authority over the region.
-
D.
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.
-
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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.