Triple
T651321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Holy Days |
E11350
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Jewish religious observance period |
C2503
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Jewish religious observance period Context triple: [High Holy Days, instanceOf, Jewish religious observance period]
-
A.
Jewish holiday
chosen
A Jewish holiday is a recurring religious and cultural observance in Judaism, marked by specific rituals, prayers, and traditions that commemorate historical events, spiritual themes, or agricultural cycles.
-
B.
period in the Christian liturgical year
A period in the Christian liturgical year is a distinct, recurring span of time marked by specific theological themes, rituals, and observances that structure the worship and spiritual life of the Church.
-
C.
Islamic religious festival
An Islamic religious festival is a recurring sacred occasion in Islam, marked by specific rituals, communal worship, and cultural practices that commemorate key events in Islamic belief and history.
-
D.
Christian religious festival
A Christian religious festival is a recurring celebration within the Christian tradition that commemorates key events in the life of Jesus Christ, the saints, or central doctrines of the faith through worship, ritual, and communal observance.
-
E.
biblical festival
A biblical festival is a recurring sacred celebration ordained in the Bible, marked by specific rituals, offerings, and communal practices that commemorate key events in God’s relationship with His people.
- F. None of above.
Provenance (1 batch)
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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.