Triple
T36001567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Days of Awe |
E1041144
|
entity |
| Predicate | liturgicalTextEmphasis |
P12432
|
FINISHED |
| Object | Machzor |
—
|
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: Machzor | Statement: [Days of Awe, liturgicalTextEmphasis, Machzor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalTextEmphasis Context triple: [Days of Awe, liturgicalTextEmphasis, Machzor]
-
A.
liturgicalText
chosen
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
B.
liturgicalTextsFoundIn
Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
-
C.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
-
D.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
E.
liturgicalLevel
Indicates the relative degree of importance or solemnity assigned to a liturgical celebration or observance within a religious tradition.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.