Triple
T28656929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P75 |
E725358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Greek New Testament papyrus manuscript |
C26547
|
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 papyrus manuscript Context triple: [P75, instanceOf, Greek New Testament papyrus manuscript]
-
A.
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.
-
B.
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.
-
C.
manuscript of the Pauline Epistles
chosen
A manuscript of the Pauline Epistles is a handwritten document containing some or all of the New Testament letters traditionally attributed to the Apostle Paul, often reflecting specific textual, linguistic, and historical transmission features.
-
D.
Aramaic papyri
Aramaic papyri are ancient documents written in the Aramaic language on papyrus, typically comprising letters, legal contracts, and administrative records that illuminate the social, economic, and political life of Near Eastern communities.
-
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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:55 a.m.