Triple
T21725424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Theological Federation |
E536262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theological federation |
C18901
|
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 federation Context triple: [Cambridge Theological Federation, instanceOf, theological federation]
-
A.
theological consortium
chosen
A theological consortium is a collaborative association of religious scholars, institutions, and organizations dedicated to advancing the study, dialogue, and application of theological thought across traditions.
-
B.
federated church
A federated church is a single local congregation formed by the union of two or more distinct denominational bodies that worship and minister together while maintaining ties to their respective parent denominations.
-
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.
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.
-
E.
Protestant federation
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:48 p.m.