Triple
T32836962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | editions of the Epistles of Phalaris |
E839859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scholarly edition corpus |
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: scholarly edition corpus Context triple: [editions of the Epistles of Phalaris, instanceOf, scholarly edition corpus]
-
A.
bibliographical corpus
A bibliographical corpus is a structured collection of bibliographic records or references, typically compiled for systematic analysis, cataloging, or research on published works.
-
B.
classical text editions
chosen
Classical text editions are scholarly publications that present ancient or historically significant works with critically established texts, annotations, translations, and contextual commentary.
-
C.
textual scholarship project
A textual scholarship project is a systematic, research-driven endeavor focused on discovering, analyzing, editing, and interpreting texts (often historical or literary) to establish reliable versions and deepen understanding of their production, transmission, and reception.
-
D.
documentation corpus
A documentation corpus is a structured collection of written materials, such as manuals, guides, and reference texts, compiled to provide comprehensive information and support for a specific domain, product, or system.
-
E.
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.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:16 a.m.