Triple
T19636995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mysteria Gloriosa |
E471422
|
entity |
| Predicate | dayTraditionallyPrayed |
P86735
|
FINISHED |
| Object | Wednesday |
—
|
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: Wednesday | Statement: [Mysteria Gloriosa, dayTraditionallyPrayed, Wednesday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayTraditionallyPrayed Context triple: [Mysteria Gloriosa, dayTraditionallyPrayed, Wednesday]
-
A.
dailyPrayerName
Indicates the specific named prayer associated with a given day in a recurring daily prayer schedule.
-
B.
numberOfDailyPrayers
Indicates the specific count of prayers that are performed each day.
-
C.
dayRelativeToEaster
Indicates the temporal offset of a given day relative to the date of Easter in a specific year (e.g., days before or after Easter Sunday).
-
D.
liturgicalFeastDay
chosen
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
E.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641070528819085663c439f50148e |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.