Triple

T19661971
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Egypt E472102 entity
Predicate instanceOf P0 FINISHED
Object Roman provincial 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: Roman provincial diocese
Context triple: [Diocese of Egypt, instanceOf, Roman provincial 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. Roman province
    A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
  • C. Roman Catholic ecclesiastical province
    A Roman Catholic ecclesiastical province is a territorial grouping of dioceses under the leadership of a metropolitan archbishop, established to coordinate pastoral activity and governance within a defined region of the Church.
  • D. province of the Byzantine Empire
    A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
  • 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_69d8e51395348190ac1416d46dfc6db0 completed April 10, 2026, 11:54 a.m.
Created at: April 10, 2026, 1:45 p.m.