Triple
T28244696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ruler of a prince-bishopric |
C49358
|
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 a prince-bishopric Context triple: [Prince-Bishop of Lübeck, instanceOf, ruler of a prince-bishopric]
-
A.
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.
-
B.
Prince-elector of the Holy Roman Empire
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.
prelate of the Holy Roman Empire
chosen
A prelate of the Holy Roman Empire was a high-ranking ecclesiastical dignitary who held imperial immediacy, combining spiritual authority with temporal power as a prince of the Empire.
-
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.
feudatory ruler
A feudatory ruler is a subordinate sovereign who governs a territory and owes allegiance, tribute, and military support to a more powerful overlord or suzerain.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11 p.m.