Triple
T8896363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson–Pierpont Byzantine Greek New Testament editions |
E211814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | majority text edition |
C25257
|
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: majority text edition Context triple: [Robinson–Pierpont Byzantine Greek New Testament editions, instanceOf, majority text edition]
-
A.
critical edition project
A critical edition project is a scholarly endeavor that collects, compares, and annotates all significant textual witnesses of a work to establish a reliable text and provide contextual commentary.
-
B.
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.
-
C.
annotated edition
An annotated edition is a version of a text that includes explanatory notes, commentary, and other scholarly or contextual information to aid understanding and interpretation.
-
D.
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.
-
E.
textual variant
A textual variant is any difference in wording, spelling, punctuation, or formatting found among multiple copies or editions of the same text.
- F. None of above. chosen
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.