Triple
T31699211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kritik der paulinischen Briefe |
E809005
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | biblical criticism work |
C26783
|
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: biblical criticism work Context triple: [Kritik der paulinischen Briefe, instanceOf, biblical criticism work]
-
A.
work of biblical criticism
chosen
A work of biblical criticism is a scholarly text that analyzes the Bible’s origins, composition, historical context, literary features, and theological claims using critical methods and academic tools.
-
B.
biblical critic
A biblical critic is a scholar who analyzes biblical texts using historical, literary, linguistic, and theological methods to understand their origins, context, and meaning.
-
C.
textual criticism
Textual criticism is the scholarly discipline that examines and compares different manuscript versions of a text to reconstruct its most accurate original form and understand its transmission over time.
-
D.
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.
-
E.
critical edition of the Hebrew Bible
A critical edition of the Hebrew Bible is a scholarly reconstruction of the biblical text that compares and evaluates all major manuscripts and textual witnesses to present the most reliable form of the original writings, accompanied by an apparatus documenting significant variants.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:11 p.m.