Triple
T5223921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scholia on Proverbs |
E117937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early Christian exegetical work |
C13506
|
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: early Christian exegetical work Context triple: [Scholia on Proverbs, instanceOf, early Christian exegetical work]
-
A.
early Christian work
chosen
An early Christian work is a text or artifact produced by followers of Jesus in the first centuries CE that expresses, develops, or transmits emerging Christian beliefs, practices, and community life.
-
B.
Late Antique Christian
A Late Antique Christian is an adherent of Christianity living between roughly the 3rd and 8th centuries CE, shaped by the Roman Empire’s transformation, emerging Christian institutions, and evolving theological and cultural debates.
-
C.
method of biblical exegesis
A method of biblical exegesis is a systematic approach or set of interpretive principles used to analyze, explain, and derive meaning from biblical texts within their historical, literary, and theological contexts.
-
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.
Biblical manuscript tradition
The biblical manuscript tradition encompasses the historical transmission, copying, preservation, and variation of biblical texts across languages, regions, and centuries.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:48 p.m.