Triple
T10061369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Book of Resolutions of The United Methodist Church |
E212997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church policy document |
C11625
|
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: church policy document Context triple: [The Book of Resolutions of The United Methodist Church, instanceOf, church policy document]
-
A.
church document
A church document is an official written record or statement produced by a religious institution to communicate doctrine, policy, liturgy, or administrative decisions.
-
B.
ecclesiastical document
chosen
An ecclesiastical document is an official written instrument issued or authorized by a church authority that records, communicates, or regulates matters of faith, doctrine, worship, or church governance.
-
C.
religious policy statement
A religious policy statement is an official document that outlines an organization’s principles, rules, and positions regarding religious beliefs, practices, and accommodations.
-
D.
policy of the Church of England
The policy of the Church of England is the body of principles, rules, and official positions that guide its governance, doctrine, worship, and public engagement.
-
E.
church organization
A church organization is a structured religious entity that coordinates worship, spiritual leadership, community services, and administrative functions for a specific faith community.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 8:57 p.m.