Triple
T25836906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume Jean Joseph Marie de Nassau |
E650826
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hereditary Grand Duke |
C31952
|
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: Hereditary Grand Duke Context triple: [Guillaume Jean Joseph Marie de Nassau, instanceOf, Hereditary Grand Duke]
-
A.
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.
-
B.
Grand Duke of Oldenburg
The Grand Duke of Oldenburg was the hereditary sovereign ruler of the Grand Duchy of Oldenburg, a German state that existed from 1815 to 1918 within the German Confederation and later the German Empire.
-
C.
Duke of Luxembourg
The Duke of Luxembourg is a noble title historically associated with the ruler or high-ranking aristocrat of the Luxembourg region, often linked to European dynastic and political affairs.
-
D.
Grand Duke
chosen
A Grand Duke is a noble ruler or high-ranking aristocrat who governs a grand duchy, ranking below a king but above most other nobles in a monarchical hierarchy.
-
E.
Grand Duke of Mecklenburg-Schwerin
The Grand Duke of Mecklenburg-Schwerin was the hereditary sovereign ruler of the Grand Duchy of Mecklenburg-Schwerin, a German state within the Holy Roman Empire and later the German Confederation and German Empire, until the monarchy’s abolition in 1918.
- 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_69e7ab38086081908f3a8e7e0c6efd83 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:46 a.m.