Triple
T3117746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paschal canon |
E65101
|
entity |
| Predicate | liturgicalTimeOfDay |
P9495
|
FINISHED |
| Object | night |
—
|
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: night | Statement: [Paschal canon, liturgicalTimeOfDay, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalTimeOfDay Context triple: [Paschal canon, liturgicalTimeOfDay, night]
-
A.
liturgicalMoment
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.
hasLiturgicalPeriod
Indicates that something is associated with, occurs during, or is assigned to a specific liturgical period within a religious calendar.
-
D.
liturgicalSetting
chosen
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e73cc88190846ef37ccf1a0de7 |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.