Triple
T37648411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser Feasts and Fasts |
E937103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Episcopal Church liturgical resource |
C64337
|
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: Episcopal Church liturgical resource Context triple: [Lesser Feasts and Fasts, instanceOf, Episcopal Church liturgical resource]
-
A.
Episcopal Church resource
chosen
An Episcopal Church resource is any material, tool, or reference—such as liturgical texts, educational curricula, or pastoral guides—created to support the worship, governance, teaching, and mission of the Episcopal Church.
-
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.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
-
D.
United Methodist Church publication
A United Methodist Church publication is an official or affiliated printed or digital resource that communicates the denomination’s theology, news, teachings, and guidance to its members and the wider public.
-
E.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.