Triple
T3490028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-elector of Mainz |
E73704
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince-elector |
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: prince-elector Context triple: [Prince-elector of Mainz, instanceOf, prince-elector]
-
A.
prince-electorate
A prince-electorate is a sovereign or semi-sovereign ruler within the Holy Roman Empire who held the hereditary right to participate in the election of the emperor.
-
B.
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.
-
C.
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.
-
D.
Duke of Prussia
The Duke of Prussia was a hereditary noble title held by the rulers of the Duchy of Prussia, originally a fief of the Polish Crown that later became the core territory of the Kingdom of Prussia.
-
E.
Elector of Hanover
The Elector of Hanover was the ruler of the Electorate of Hanover within the Holy Roman Empire, holding one of the empire’s prestigious electoral titles and, from 1714, simultaneously serving as the monarch of Great Britain.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:18 p.m.