Triple
T1247544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prayer of Manasseh |
E26801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | deuterocanonical text (in some traditions) |
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: deuterocanonical text (in some traditions) Context triple: [Prayer of Manasseh, instanceOf, deuterocanonical text (in some traditions)]
-
A.
New Testament tradition
New Testament tradition is the body of interpretive practices, teachings, and communal memories through which Christian communities have transmitted, received, and reshaped the writings and theology of the New Testament across history.
-
B.
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.
-
C.
biblical canon subdivision
A biblical canon subdivision is a distinct grouping or category within the collection of authoritative biblical books, such as the Pentateuch, Historical Books, Prophets, Gospels, or Epistles.
-
D.
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.
-
E.
holy book
A holy book is a written text or collection of writings regarded by a religious community as divinely inspired or authoritative in matters of faith, morality, and spiritual practice.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.