Triple
T33835428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neot-tide |
E867218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian liturgical feast period |
C1339
|
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: Christian liturgical feast period Context triple: [Neot-tide, instanceOf, Christian liturgical feast period]
-
A.
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.
-
B.
period in the Christian liturgical year
chosen
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.
day in the Christian liturgical year
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.
-
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.
Christian liturgical hour
A Christian liturgical hour is a fixed time of day designated for structured prayer and worship within the Liturgy of the Hours, marking the sanctification of the day through psalms, readings, and hymns.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.