Triple
T4003728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Tuesday |
E89473
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | day in the Christian liturgical calendar |
C14353
|
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: day in the Christian liturgical calendar Context triple: [Holy Tuesday, instanceOf, day in the Christian liturgical calendar]
-
A.
day in the Christian liturgical year
chosen
A day in the Christian liturgical year is a specific calendar date assigned particular religious significance, observances, and readings within the cycle of Christian worship.
-
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.
Christian liturgical season
A Christian liturgical season is a distinct, recurring period in the church year marked by specific theological themes, scriptures, prayers, and worship practices that shape the spiritual life and observances of the Christian community.
-
D.
liturgical calendar
A liturgical calendar is a structured schedule of religious seasons, feasts, and observances that organizes worship and devotional practices throughout the year.
-
E.
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.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:34 p.m.