Triple
T17815990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick I of Saxony |
E444842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Landgrave of Thuringia |
C39181
|
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: Landgrave of Thuringia Context triple: [Frederick I of Saxony, instanceOf, Landgrave of Thuringia]
-
A.
Landgrave of Hesse-Kassel
The Landgrave of Hesse-Kassel was the hereditary ruler of the German principality of Hesse-Kassel, holding both territorial authority and noble rank within the Holy Roman Empire and its successor states.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Prince of Transylvania
A Prince of Transylvania is the sovereign or semi-sovereign ruler of the historical region of Transylvania, traditionally holding political, military, and often symbolic authority over its territories and people.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:14 a.m.