Triple
T2113113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First fruits (Bikkurim) |
E42547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical religious practice |
C757
|
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: biblical religious practice Context triple: [First fruits (Bikkurim), instanceOf, biblical religious practice]
-
A.
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.
-
B.
religious ritual
chosen
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.
-
C.
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.
-
D.
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.
-
E.
Biblical discourse
Biblical discourse is the structured communication—spoken, written, or interpretive—that engages with, explains, or applies the texts, themes, and theology of the Bible within specific historical, cultural, and religious contexts.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:43 p.m.