Triple

T28692607
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Sirmium E729326 entity
Predicate instanceOf P0 FINISHED
Object ancient Christian bishopric 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 bishopric
Context triple: [Diocese of Sirmium, instanceOf, ancient Christian bishopric]
  • A. ancient Christian episcopal see chosen
    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.
  • B. medieval Christian bishopric
    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. 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.
  • D. 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.
  • E. 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.
  • 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_69f043e60b6c8190ac2cd042e77fe6e9 completed April 28, 2026, 5:21 a.m.
Created at: April 28, 2026, 5:37 a.m.