Triple
T7186995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Día de Muertos |
E167597
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious and cultural observance |
C20923
|
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: religious and cultural observance Context triple: [Día de Muertos, instanceOf, religious and cultural observance]
-
A.
Jewish observance
Jewish observance is the practice of religious commandments, rituals, customs, and ethical principles rooted in Jewish law and tradition, guiding daily life, worship, and communal identity.
-
B.
Christian religious observance
Christian religious observance is the practice of worship, rituals, and disciplines—such as prayer, sacraments, and holy days—through which Christians express devotion to God and live out their faith in community and daily life.
-
C.
religious tradition
A religious tradition is an enduring, socially shared system of beliefs, practices, narratives, and institutions that shapes how a community understands and relates to the sacred, the moral order, and ultimate meaning.
-
D.
religious ritual
A religious ritual is a structured, symbolic sequence of actions, words, and objects performed within a faith tradition to express devotion, mark sacred events, or reinforce spiritual beliefs and communal identity.
-
E.
Christian observance
A Christian observance is a religious practice, ritual, or commemoration—such as a holiday, sacrament, or liturgical season—through which Christians collectively remember, celebrate, or express key aspects of their faith.
- F. None of above. chosen
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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.