Triple
T7060604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbot of Monte Cassino |
E164205
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic clerical role |
C6233
|
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 clerical role Context triple: [Abbot of Monte Cassino, instanceOf, Catholic clerical role]
-
A.
clergy role
A clergy role represents an authorized religious position responsible for leading worship, providing spiritual guidance, and performing sacred rituals within a faith community.
-
B.
office in the Catholic Church
chosen
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.
-
C.
Anglican clerical position
An Anglican clerical position is an official role within the Anglican Church’s ordained or licensed ministry structure, encompassing responsibilities for worship, pastoral care, administration, and spiritual leadership in a parish or wider ecclesiastical jurisdiction.
-
D.
traditional Catholic priestly society
A traditional Catholic priestly society is an organized community of clergy and often associated laity dedicated to preserving and promoting the liturgy, doctrine, and spiritual practices of the Catholic Church as they were handed down before recent reforms.
-
E.
Christian religious office
A Christian religious office is an institutional role or position within a Christian church or denomination, endowed with specific spiritual, liturgical, and administrative responsibilities and authority.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:38 p.m.