Triple
T27818900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Church in Montana |
E702757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic ecclesiastical jurisdictional structure |
C15587
|
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: Catholic ecclesiastical jurisdictional structure Context triple: [Roman Catholic Church in Montana, instanceOf, Catholic ecclesiastical jurisdictional structure]
-
A.
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.
-
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.
Roman Catholic territorial jurisdiction
chosen
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.
-
D.
ecclesiastical authority
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
-
E.
office in the Catholic Church
An office in the Catholic Church is an established position of ecclesiastical responsibility, authority, or service, entrusted to a person for the governance, ministry, or administration of the Church.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:47 p.m.