Triple
T4367748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Saxe-Eisenach |
E98818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ernestine duchy |
C15811
|
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: Ernestine duchy Context triple: [Duchy of Saxe-Eisenach, instanceOf, Ernestine duchy]
-
A.
King of Westphalia
The King of Westphalia was the sovereign ruler of the short-lived Kingdom of Westphalia (1807–1813), a Napoleonic client state in central Europe governed primarily by Napoleon’s brother Jérôme Bonaparte.
-
B.
Count of Luxembourg
A Count of Luxembourg is a noble title historically held by the feudal rulers of the County of Luxembourg, signifying territorial lordship, aristocratic status, and dynastic authority within the medieval and early modern European nobility.
-
C.
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.
-
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 Lorraine
The Duke of Lorraine is a noble title historically held by the sovereign ruler of the Duchy of Lorraine, a strategically important region in northeastern France that played a key role in European dynastic and territorial politics.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:17 p.m.