Triple
T211451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission for Confidential Matters |
E4727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | commission of the Roman Curia |
C1015
|
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: commission of the Roman Curia Context triple: [Commission for Confidential Matters, instanceOf, commission of the Roman Curia]
-
A.
organ of the Holy See
chosen
An organ of the Holy See is an official body, institution, or office that acts on behalf of the Holy See to exercise its spiritual, administrative, diplomatic, or judicial functions within the Catholic Church and in relations with states and international organizations.
-
B.
Catholic Church council
A Catholic Church council is a formal assembly of bishops and other church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
C.
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.
-
D.
Catholic Church
The Catholic Church is a worldwide Christian religious institution, led by the Pope, that traces its origins to Jesus Christ and the apostles and is characterized by a hierarchical structure, sacramental worship, and a unified body of doctrine.
-
E.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.