Triple
T890192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick V, Elector Palatine |
E19221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prince-elector of the Holy Roman Empire |
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 the Holy Roman Empire Context triple: [Frederick V, Elector Palatine, instanceOf, Prince-elector of the Holy Roman Empire]
-
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.
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.
-
C.
prince-bishopric
A prince-bishopric is a territorial state within the Holy Roman Empire or similar realms where a bishop held both secular princely authority and ecclesiastical jurisdiction over the same region.
-
D.
Governor-General of the Habsburg Netherlands
The Governor-General of the Habsburg Netherlands was the monarch’s chief representative who governed the provinces on behalf of the Habsburg ruler, overseeing administration, military affairs, and the implementation of imperial policy.
-
E.
princely office
A princely office is an institutional role or position held by a prince or princely figure, encompassing the authority, duties, and ceremonial functions associated with governing or representing a principality or royal domain.
- F. None of above. chosen
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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.