Triple
T36888955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Bardstown |
E911687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic Catholic jurisdiction |
C15374
|
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 Catholic jurisdiction Context triple: [Diocese of Bardstown, instanceOf, historic Catholic jurisdiction]
-
A.
Roman Catholic territorial jurisdiction
A Roman Catholic territorial jurisdiction is an ecclesiastical region, such as a diocese or archdiocese, over which a bishop or equivalent church authority exercises pastoral and administrative governance.
-
B.
ecclesiastical jurisdiction
An ecclesiastical jurisdiction is a defined territorial or personal area of authority within a religious organization, governed by church law and overseen by designated clerical leaders.
-
C.
former Catholic diocese
chosen
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.
-
D.
Catholic Church administrative division
A Catholic Church administrative division is a geographically defined ecclesiastical jurisdiction, such as a diocese or parish, overseen by church authorities to organize governance, pastoral care, and liturgical life.
-
E.
Latin Catholic diocese
A Latin Catholic diocese is a territorial ecclesiastical jurisdiction of the Latin Church, governed by a bishop who oversees the pastoral care, administration, and spiritual life of Catholics 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.