Triple
T2897354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARCIC |
E63972
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological dialogue commission |
C2439
|
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: theological dialogue commission Context triple: [ARCIC, instanceOf, theological dialogue commission]
-
A.
ecumenical dialogue commission
chosen
An ecumenical dialogue commission is a formal body composed of representatives from different Christian traditions tasked with fostering theological discussion, mutual understanding, and cooperative initiatives toward greater church unity.
-
B.
theological commission
A theological commission is a formally appointed group of experts tasked with studying, evaluating, and advising on doctrinal, moral, or ecclesial questions within a religious tradition.
-
C.
communion of churches
A communion of churches is an association of autonomous Christian churches that recognize each other’s ministries and sacraments, and share a common faith, doctrine, and ecclesial life while retaining their own governance structures.
-
D.
theological library
A theological library is a specialized collection of books, manuscripts, digital resources, and reference materials focused on religious studies, sacred texts, theology, and related disciplines, organized to support research, education, and spiritual inquiry.
-
E.
theological journal
A theological journal is a periodical publication that presents scholarly research, critical essays, and reflections on religious beliefs, doctrines, practices, and their implications for faith and society.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
Created at: March 6, 2026, 10:08 p.m.