Triple
T22327839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baskerville’s classical editions |
E551946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classical text editions |
C46112
|
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: classical text editions Context triple: [Baskerville’s classical editions, instanceOf, classical text editions]
-
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.
biblical text edition
A biblical text edition is a curated version of the Bible that presents a specific text form, often with scholarly annotations, critical apparatus, translations, and editorial decisions to support study, interpretation, or liturgical use.
-
C.
classics journal
A classics journal is a periodical publication that features scholarly research, critical essays, reviews, and discussions on the literature, history, languages, philosophy, and culture of the ancient Greek and Roman worlds.
-
D.
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.
-
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. 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.