Triple
T24168250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nekresi episcopal see |
E599053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic bishopric |
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: historic bishopric Context triple: [Nekresi episcopal see, instanceOf, historic bishopric]
-
A.
historic parish
A historic parish is a former ecclesiastical or civil territorial unit, typically centered around a church, whose boundaries and institutions reflect the administrative and social organization of a past period.
-
B.
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.
-
C.
historic church body
A historic church body is a long-established Christian denomination or ecclesiastical organization whose identity, structure, and traditions have been shaped over centuries of continuous institutional and theological development.
-
D.
historic pulpit
A historic pulpit is an elevated, often ornately crafted platform within a religious or civic space from a past era, used for delivering sermons, speeches, or public addresses and valued for its architectural, cultural, and historical significance.
-
E.
historic establishment
A historic establishment is a long-standing place of business or institution recognized for its significant role, continuity, and influence in a particular community or period of history.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 11:33 p.m.