Triple
T9844505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Qurbana |
E239304
|
entity |
| Predicate | liturgicalSeasonUse |
P25898
|
FINISHED |
| Object | Sundays |
—
|
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: Sundays | Statement: [Holy Qurbana, liturgicalSeasonUse, Sundays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalSeasonUse Context triple: [Holy Qurbana, liturgicalSeasonUse, Sundays]
-
A.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
B.
liturgicalSeasonVariation
Indicates that something changes or differs depending on the liturgical season within a religious calendar or worship cycle.
-
C.
liturgicalSeasonContext
chosen
Indicates the specific liturgical season within which a religious action, event, or text takes place or is understood.
-
D.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
E.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35dc29c819080203be5b904dc9d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.