Triple
T37174950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William I, Duke of Jülich |
E921013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Duke of Jülich |
C63971
|
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: Duke of Jülich Context triple: [William I, Duke of Jülich, instanceOf, Duke of Jülich]
-
A.
Duke of Holstein
The Duke of Holstein is a noble title historically held by rulers of the duchy of Holstein in northern Germany, often intertwined with the Danish crown and regional power politics in Schleswig-Holstein.
-
B.
Duke of Cleves
The Duke of Cleves is a noble title historically held by the ruler of the Duchy of Cleves, a territorial principality within the Holy Roman Empire located in what is now western Germany and the Netherlands.
-
C.
Duke of Lauenburg
The Duke of Lauenburg is a noble title historically associated with the ruler of the Duchy of Lauenburg, a small German principality within the Holy Roman Empire and later states of the German Confederation.
-
D.
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.
-
E.
Duke of Danzig
The Duke of Danzig is a noble title historically associated with the governance, representation, or symbolic lordship over the city and surrounding region of Danzig (modern-day Gdańsk), often reflecting shifting political control in Central and Eastern Europe.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.