Triple
T8896155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majority text |
E211809
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New Testament textual tradition |
C1984
|
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: New Testament textual tradition Context triple: [Majority text, instanceOf, New Testament textual tradition]
-
A.
Biblical manuscript tradition
chosen
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
-
B.
sources for New Testament textual criticism
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.
-
C.
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.
-
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.
New Testament studies issue
A New Testament studies issue is a scholarly problem, question, or debate arising from the historical, literary, theological, or textual analysis of the New Testament writings and their early Christian context.
- 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.