Triple
T26528857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenebrae Responsories |
E670763
|
entity |
| Predicate | liturgicalDayGroup |
P160608
|
FINISHED |
| Object | Triduum |
—
|
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: Triduum | Statement: [Tenebrae Responsories, liturgicalDayGroup, Triduum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalDayGroup Context triple: [Tenebrae Responsories, liturgicalDayGroup, Triduum]
-
A.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
B.
liturgicalCelebration
Indicates that one entity conducts or is associated with a formal act of worship or religious rite in honor of another entity, event, or sacred mystery.
-
C.
liturgicalFeastDay
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
D.
liturgicalSequence
Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
-
E.
liturgicalUnitType
Indicates the specific kind or category of a liturgical unit within a religious or worship context.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f4ecb48190a463bde18f550279 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:34 a.m.