Triple
T34589891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation of the Blessed Virgin Mary |
E888148
|
entity |
| Predicate | liturgicalHourEmphasis |
P24082
|
FINISHED |
| Object | Vespers |
—
|
NE NERFINISHED |
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: Vespers | Statement: [Visitation of the Blessed Virgin Mary, liturgicalHourEmphasis, Vespers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalHourEmphasis Context triple: [Visitation of the Blessed Virgin Mary, liturgicalHourEmphasis, Vespers]
-
A.
liturgicalMoment
chosen
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
-
B.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
C.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
D.
liturgicalLevel
Indicates the relative degree of importance or solemnity assigned to a liturgical celebration or observance within a religious tradition.
-
E.
liturgicalNote
Indicates a relationship where a note or comment is specifically associated with liturgical practice, text, or ritual.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720cc1bfc8190a16118e3af8e9316 |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.