Triple
T9526383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Israel liturgy |
E229770
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious text tradition |
C1830
|
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 text tradition Context triple: [Beta Israel liturgy, instanceOf, religious text tradition]
-
A.
religious scripture
A religious scripture is a revered written text or collection of texts that a faith community regards as divinely inspired or authoritative in matters of belief, morality, and spiritual practice.
-
B.
religious literature
chosen
Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
-
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 text carrier
A religious text carrier is an entity (person, object, or medium) that transports, preserves, or conveys sacred writings from one place, time, or audience to another.
-
E.
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.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:59 p.m.