Triple
T12108916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clemens Wenceslaus of Saxony |
E288371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Elector of Trier |
C5572
|
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: Elector of Trier Context triple: [Clemens Wenceslaus of Saxony, instanceOf, Elector of Trier]
-
A.
King of the Romans
The King of the Romans was the title used by the elected ruler of the Holy Roman Empire, designating him as emperor-designate pending papal coronation as Holy Roman Emperor.
-
B.
King of Lotharingia
The King of Lotharingia is the sovereign ruler of the medieval kingdom of Lotharingia, governing its territories, administering justice, leading its armies, and representing its authority within the broader context of the Frankish and later Holy Roman Empire realms.
-
C.
Duke of Lotharingia
The Duke of Lotharingia is a high-ranking noble who governs the historical region of Lotharingia, wielding military, judicial, and administrative authority on behalf of the sovereign.
-
D.
Prince-elector of the Holy Roman Empire
chosen
A Prince-elector of the Holy Roman Empire was a high-ranking territorial ruler or ecclesiastical prince endowed with the exclusive right to participate in the election of the Holy Roman Emperor.
-
E.
prince of the Holy Roman Empire
A prince of the Holy Roman Empire was a secular or ecclesiastical ruler who held immediate authority under the emperor, possessing territorial sovereignty and a vote in the Imperial Diet.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.