Triple
T2262897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutheran World Federation |
E50078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global communion of churches |
C4014
|
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: global communion of churches Context triple: [Lutheran World Federation, instanceOf, global communion of churches]
-
A.
communion of churches
chosen
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.
-
B.
communion of particular churches
A communion of particular churches is a unified fellowship of distinct local or ritual churches that share the same faith, sacraments, and ecclesial governance while retaining their own liturgical and cultural traditions.
-
C.
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.
-
D.
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.
-
E.
Christian communion
Christian communion is a sacramental ritual in which believers share bread and wine (or equivalents) to remember and participate in the body and blood of Jesus Christ, symbolizing unity with Him and with one another.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:48 p.m.