Triple
T24940328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William V, Duke of Bavaria |
E623434
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of Bavaria |
C13744
|
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: ruler of Bavaria Context triple: [William V, Duke of Bavaria, instanceOf, ruler of Bavaria]
-
A.
Bavarian monarch
A Bavarian monarch is the sovereign ruler of Bavaria, historically holding supreme political authority and symbolic leadership over the Bavarian state and its people.
-
B.
Bavarian prince
A Bavarian prince is a male member of the royal or formerly ruling house of Bavaria, traditionally holding hereditary titles, privileges, and social status within the region’s historical monarchy.
-
C.
Duke of Bavaria
chosen
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.
-
D.
King of Saxony
The King of Saxony is the hereditary monarch who historically ruled the Kingdom of Saxony, holding supreme authority over its government, military, and foreign affairs within the German states.
-
E.
King of Württemberg
The King of Württemberg was the hereditary monarch and head of state of the Kingdom of Württemberg, a German state that existed from 1806 to 1918 within the Holy Roman Empire’s successor systems and later the German Empire.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:30 a.m.