Triple
T37969240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Regensburg |
E947233
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | secular princely office |
C2451
|
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: secular princely office Context triple: [Prince-Bishop of Regensburg, instanceOf, secular princely office]
-
A.
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.
-
B.
Polish noble office
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
-
C.
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.
-
D.
dynastic office
A dynastic office is a formal position of authority or responsibility that is inherited within a family line, typically passing from one generation to the next.
-
E.
prince-bishopric
chosen
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.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.