Triple
T28719216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verona List |
E730044
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late Roman document |
C24468
|
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: late Roman document Context triple: [Verona List, instanceOf, late Roman document]
-
A.
Roman administrative text
A Roman administrative text is a written document produced by Roman authorities to record, regulate, or communicate matters of governance, such as laws, edicts, census data, tax records, and official correspondence.
-
B.
late Roman legal codex
A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
-
C.
late antique manuscript
chosen
A late antique manuscript is a handwritten document produced between roughly the 3rd and 8th centuries CE, typically on papyrus or parchment, reflecting the transitional cultural, religious, and artistic practices of the late Roman and early medieval worlds.
-
D.
late antique literature
Late antique literature encompasses the diverse body of Greek, Latin, and other regional writings produced roughly between the third and eighth centuries CE, reflecting the cultural, religious, and political transformations of the late Roman and early Byzantine worlds.
-
E.
Vetus Latina manuscript
A Vetus Latina manuscript is a handwritten document preserving an Old Latin (pre-Vulgate) translation of biblical texts used in the Western Church before Jerome’s standardized Vulgate.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 5:52 a.m.