Triple
T4185983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of St Andrews |
E88312
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Scottish bishopric |
C14801
|
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: medieval Scottish bishopric Context triple: [Bishopric of St Andrews, instanceOf, medieval Scottish bishopric]
-
A.
medieval Scottish churchman
A medieval Scottish churchman is a cleric or ecclesiastical leader in Scotland during the Middle Ages, involved in religious, political, and social affairs within the Church and broader society.
-
B.
Anglo-Saxon bishop
An Anglo-Saxon bishop was a high-ranking ecclesiastical leader in early medieval England responsible for overseeing a diocese, administering sacraments, guiding clergy and laity, and often advising kings in both religious and political matters.
-
C.
historic county of Scotland
A historic county of Scotland is a traditional territorial division that once served as an administrative and cultural unit, often retaining significance for identity, geography, and historical reference despite no longer having formal governmental functions.
-
D.
Bishop of Ely
The Bishop of Ely is a senior ecclesiastical leader in the Church of England who oversees the Diocese of Ely, providing spiritual, administrative, and pastoral leadership within that region.
-
E.
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.
- 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_69aed9477e8c81908bcb862d2db55b1d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.