Triple
T8876265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernest Louis, Grand Duke of Hesse |
E211292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | grand duke |
C9978
|
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: grand duke Context triple: [Ernest Louis, Grand Duke of Hesse, instanceOf, grand duke]
-
A.
Grand Duke of Hesse
chosen
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.
-
B.
Grand Duke of Russia
A Grand Duke of Russia was a male member of the Russian imperial family, typically a son or grandson of a reigning emperor, who held high dynastic rank and status without necessarily exercising sovereign rule.
-
C.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions and alliances with neighboring states.
-
D.
Grand Duke of Lithuania
The Grand Duke of Lithuania was the sovereign ruler of the Grand Duchy of Lithuania, holding supreme political, military, and judicial authority over its territories and often engaging in dynastic unions with neighboring states.
-
E.
Duke of Courland
The Duke of Courland was the hereditary ruler of the Duchy of Courland and Semigallia, a semi-autonomous Baltic state under Polish-Lithuanian suzerainty from the 16th to 18th centuries.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:52 p.m.