Triple
T26771631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Leighlin (historical) |
E675093
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval diocese |
C47897
|
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 diocese Context triple: [Diocese of Leighlin (historical), instanceOf, medieval diocese]
-
A.
medieval Christian bishopric
chosen
A medieval Christian bishopric is an ecclesiastical jurisdiction governed by a bishop, encompassing both the spiritual authority over clergy and laity and the temporal control of lands, revenues, and often political influence within a defined region.
-
B.
medieval church
A medieval church is a religious building from the Middle Ages, typically characterized by stone construction, vaulted ceilings, stained glass windows, and architectural styles such as Romanesque or Gothic, serving as a center for worship and community life.
-
C.
medieval Scottish bishopric
A medieval Scottish bishopric was an ecclesiastical jurisdiction headed by a bishop, overseeing the spiritual, administrative, and often political affairs of the Church within a defined region of Scotland during the Middle Ages.
-
D.
late Roman diocese
A late Roman diocese was a large administrative district of the Roman Empire, grouping several provinces under the authority of a vicarius to improve governance, taxation, and imperial control.
-
E.
medieval Christian church
A medieval Christian church is a religious institution and physical structure that serves as the central place for Christian worship, community gathering, and ecclesiastical authority in medieval society.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 4:02 a.m.