Triple
T38663231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem Declaration 2008 |
E940386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Anglican confessional document |
C64664
|
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 confessional document Context triple: [Jerusalem Declaration 2008, instanceOf, Anglican confessional document]
-
A.
Anglican theology text
chosen
An Anglican theology text is a written work that systematically explores Christian doctrine, worship, and ethics from the perspective of the Anglican tradition, drawing on Scripture, reason, and tradition.
-
B.
Anglican liturgical text
An Anglican liturgical text is a formal written resource used in Anglican worship that provides structured prayers, readings, and rites for services throughout the liturgical year.
-
C.
Anglican Communion institution
An Anglican Communion institution is an organization, body, or entity formally associated with or serving the global fellowship of autonomous Anglican churches, supporting their shared mission, governance, worship, or theological identity.
-
D.
Anglican article
An Anglican article is a formal doctrinal statement within Anglicanism, most notably one of the Thirty-Nine Articles, that defines key theological beliefs and practices of the Anglican Church.
-
E.
Presbyterian polity document
A Presbyterian polity document is a formal text that outlines the governance structure, rules, procedures, and doctrinal standards by which a Presbyterian church or denomination is organized and administered.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.