Triple
T8896153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majority text |
E211809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek New Testament text-type |
C2086
|
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: Greek New Testament text-type Context triple: [Majority text, instanceOf, Greek New Testament text-type]
-
A.
critical edition of the Greek New Testament
A critical edition of the Greek New Testament is a scholarly reconstruction of the text based on systematic comparison and evaluation of all available manuscript evidence, accompanied by an apparatus documenting significant textual variants.
-
B.
Septuagint manuscript
A Septuagint manuscript is a handwritten copy of the ancient Greek translation of the Hebrew Bible (and related texts), produced and transmitted by scribes in antiquity and the medieval period.
-
C.
sources for New Testament textual criticism
chosen
Sources for New Testament textual criticism are the manuscripts, early translations, and patristic citations that provide the textual evidence used to reconstruct and evaluate the original wording of the New Testament writings.
-
D.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:54 p.m.