Triple
T37884353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglican Communion teaching on homosexuality |
E944956
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican theological controversy |
C3649
|
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: Anglican theological controversy Context triple: [Anglican Communion teaching on homosexuality, instanceOf, Anglican theological controversy]
-
A.
Puritan controversy
A Puritan controversy is a historical or theological dispute arising within Puritan communities over matters of doctrine, church governance, or moral practice that challenged established religious authority and norms.
-
B.
Anglican agency
An Anglican agency is an organization established by or affiliated with the Anglican Church to carry out its mission through activities such as education, social services, evangelism, and community development.
-
C.
movement within Anglicanism
A movement within Anglicanism is a distinct stream of thought and practice that seeks to renew, reform, or emphasize particular theological, liturgical, or social aspects of Anglican faith and church life.
-
D.
Anglican–Roman Catholic dialogue text
An Anglican–Roman Catholic dialogue text is an official or semi-official document recording theological discussions, agreements, and points of divergence between Anglican and Roman Catholic representatives in ecumenical dialogue.
-
E.
theological dispute
chosen
A theological dispute is a conflict or debate between individuals or groups over differing interpretations of religious doctrines, beliefs, or sacred texts.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.