Triple
T17306821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rejoicing of the Torah |
E420184
|
entity |
| Predicate | liturgicalEmotion |
P15357
|
FINISHED |
| Object | joy |
—
|
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: joy | Statement: [Rejoicing of the Torah, liturgicalEmotion, joy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalEmotion Context triple: [Rejoicing of the Torah, liturgicalEmotion, joy]
-
A.
liturgicalMood
chosen
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
B.
liturgicalResonance
Indicates a relationship where something echoes, reflects, or aligns with the themes, forms, or atmosphere of liturgical (formal religious) practice.
-
C.
liturgicalTheme
Indicates the religious or worship-related theme that characterizes or frames a liturgical action, text, or event.
-
D.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
liturgicalMoment
Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.