Triple
T23576132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Hippo Regius |
E580261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Christian episcopal see |
C47830
|
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: ancient Christian episcopal see Context triple: [Diocese of Hippo Regius, instanceOf, ancient Christian episcopal see]
-
A.
Anglican episcopal see
An Anglican episcopal see is the geographical area of jurisdiction and the associated office of a bishop within the Anglican Communion.
-
B.
Syriac Orthodox episcopal see
A Syriac Orthodox episcopal see is a territorial jurisdiction of the Syriac Orthodox Church overseen by a bishop, encompassing the administration of clergy, parishes, and liturgical life within its defined region.
-
C.
ancient patriarchate
An ancient patriarchate is a senior episcopal jurisdiction in early Christianity, historically led by a patriarch who held preeminent authority over a major Christian center and its surrounding territories.
-
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.
Maronite Catholic eparchy
A Maronite Catholic eparchy is a territorial jurisdiction of the Maronite Church, governed by a bishop (eparch) who oversees the pastoral care, administration, and liturgical life of Maronite Catholics within its boundaries.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 6:38 p.m.