Triple
T37788400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew used Mark as a written source |
E942018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | implication of Markan priority |
C10530
|
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: implication of Markan priority Context triple: [Matthew used Mark as a written source, instanceOf, implication of Markan priority]
-
A.
New Testament studies issue
chosen
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.
-
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.
Gospel of Mark verse
A Gospel of Mark verse is a discrete textual unit within the New Testament book of Mark that conveys a specific moment, teaching, or narrative detail about the life and ministry of Jesus.
-
D.
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.
-
E.
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.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.