Triple
T20442696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry V, Count Palatine of the Rhine |
E501435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Count Palatine of the Rhine |
C19495
|
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: Count Palatine of the Rhine Context triple: [Henry V, Count Palatine of the Rhine, instanceOf, Count 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.
Count Palatine
chosen
A Count Palatine is a noble title historically granted to a count who exercised sovereign or semi-sovereign authority within their territory, often with special judicial and administrative powers delegated directly by a monarch or emperor.
-
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 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.
-
E.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
- F. None of above.
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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:32 a.m.