Triple
T24760034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of the East |
E619410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine administrative diocese |
C19733
|
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: Byzantine administrative diocese Context triple: [Diocese of the East, instanceOf, Byzantine administrative diocese]
-
A.
late Roman diocese
chosen
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.
-
B.
ancient Christian episcopal see
An ancient Christian episcopal see is a historical bishopric that served as the central ecclesiastical jurisdiction and seat of a bishop in the early Christian Church.
-
C.
Metropolitan archeparchy
A metropolitan archeparchy is a principal Eastern Catholic ecclesiastical jurisdiction, headed by a metropolitan archbishop, that presides over its own territory and often has suffragan eparchies under its authority.
-
D.
former Catholic diocese
A former Catholic diocese is an ecclesiastical jurisdiction of the Catholic Church that once functioned as a territorial diocese but has since been suppressed, merged, or otherwise ceased to exist in its original administrative form.
-
E.
Roman Catholic diocese
A Roman Catholic diocese is a territorial division of the Church under the pastoral care and governance of a bishop, responsible for overseeing the spiritual, administrative, and sacramental life of the faithful within its boundaries.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 4:27 a.m.