Triple
T4841695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Testament Passion narratives |
E108192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian scripture pericopes |
C623
|
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 scripture pericopes Context triple: [New Testament Passion narratives, instanceOf, Christian scripture pericopes]
-
A.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
-
B.
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.
-
C.
Christian text tradition
The Christian text tradition is the historical process by which Christian writings—especially the Bible and related theological, liturgical, and devotional texts—are composed, transmitted, translated, interpreted, and canonized within Christian communities over time.
-
D.
Christian ecumenical text
A Christian ecumenical text is a written work intended to foster unity, dialogue, and shared understanding among different Christian denominations by emphasizing common beliefs and cooperative practices.
-
E.
biblical text
chosen
A biblical text is a written work that forms part of the Bible, conveying religious narratives, laws, teachings, and poetry considered sacred and authoritative within Jewish and Christian traditions.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.