Triple
T917338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorrowful Mysteries |
E19799
|
entity |
| Predicate | liturgicalDayAssociation |
P21314
|
FINISHED |
| Object | Tuesday |
—
|
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: Tuesday | Statement: [Sorrowful Mysteries, liturgicalDayAssociation, Tuesday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalDayAssociation Context triple: [Sorrowful Mysteries, liturgicalDayAssociation, Tuesday]
-
A.
liturgicalAssociation
chosen
Indicates a relationship in which one entity is connected to another through shared or relevant liturgical use, function, or context.
-
B.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
C.
hasLiturgicalDay
Indicates that a particular date, event, or context is associated with a specific liturgical day within a religious calendar.
-
D.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
E.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.