Triple
T37646229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Philipp von Schönborn |
E937044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince-elector of Mainz |
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 of Mainz Context triple: [Johann Philipp von Schönborn, instanceOf, Prince-elector of Mainz]
-
A.
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.
-
B.
Elector Palatine of the Rhine
The Elector Palatine of the Rhine was a leading prince of the Holy Roman Empire who ruled the Palatinate region along the Rhine and held one of the imperial electoral votes to choose the Holy Roman Emperor.
-
C.
Elector of Hesse
The Elector of Hesse was the sovereign ruler of the Electorate of Hesse, a German principality whose prince held the prestigious rank of elector within the Holy Roman Empire and later maintained this title as a mark of dynastic status.
-
D.
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.
-
E.
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.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.