Triple
T10045954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Commission on Christian Unity and Interreligious Concerns |
E207615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interreligious dialogue body |
C4762
|
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: interreligious dialogue body Context triple: [General Commission on Christian Unity and Interreligious Concerns, instanceOf, interreligious dialogue body]
-
A.
interfaith initiative
chosen
An interfaith initiative is a collaborative effort that brings together individuals or communities from different religious traditions to foster mutual understanding, respect, and cooperative action on shared concerns.
-
B.
interfaith center
An interfaith center is a dedicated space or organization that fosters dialogue, understanding, and collaboration among people of diverse religious and spiritual traditions.
-
C.
ecumenical dialogue commission
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.
-
D.
theological dialogue
A theological dialogue is a structured conversational exchange in which participants explore, question, and interpret religious beliefs, doctrines, and experiences in pursuit of deeper understanding or truth.
-
E.
ecumenical organization
An ecumenical organization is a group or body that promotes cooperation, dialogue, and unity among different Christian denominations while respecting their distinct traditions and beliefs.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 8:56 p.m.