Triple
T477525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord’s Prayer |
E9093
|
entity |
| Predicate | doxologyUsage |
P10005
|
FINISHED |
| Object | commonly used in Protestant traditions |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: commonly used in Protestant traditions | Statement: [Lord’s Prayer, doxologyUsage, commonly used in Protestant traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doxologyUsage Context triple: [Lord’s Prayer, doxologyUsage, commonly used in Protestant traditions]
-
A.
liturgicalUsage
chosen
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
B.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
E.
sacramentalUseOf
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
- F. None of above.
Provenance (3 batches)
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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f03f3fbc81909af6e4496d5e6c2a |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.