Triple
T25364642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blessed |
E636065
|
entity |
| Predicate | liturgicalCult |
P158469
|
FINISHED |
| Object | usually local or regional |
—
|
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: usually local or regional | Statement: [Blessed, liturgicalCult, usually local or regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalCult Context triple: [Blessed, liturgicalCult, usually local or regional]
-
A.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
-
B.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
C.
liturgicalResonance
Indicates a relationship where something echoes, reflects, or aligns with the themes, forms, or atmosphere of liturgical (formal religious) practice.
-
D.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
-
E.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
- F. None of above. chosen
Provenance (4 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_69e75a9b7cf481909f2dcdfb37d95ca7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10ce1a8819081abc0012ddfaee7 |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:36 p.m.