Triple
T5089766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Textus Receptus |
E114724
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical biblical text |
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: historical biblical text Context triple: [Textus Receptus, instanceOf, historical biblical text]
-
A.
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.
-
B.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
C.
historic script
A historic script is a system of writing used by past civilizations or cultures that records their language, ideas, and events, often preserved in artifacts, manuscripts, or inscriptions.
-
D.
biblical artifact
A biblical artifact is a physical object, such as a manuscript, inscription, tool, or relic, that is historically or culturally connected to the people, places, or events described in the Bible.
-
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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:40 p.m.