Triple
T5890747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Inscriptionum Latinarum |
E130981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | epigraphic corpus |
C9642
|
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: epigraphic corpus Context triple: [Corpus Inscriptionum Latinarum, instanceOf, epigraphic corpus]
-
A.
inscription corpus
chosen
An inscription corpus is a systematically collected and organized body of inscribed texts (such as carvings on stone, metal, or other durable materials) used for linguistic, historical, and archaeological analysis.
-
B.
ancient inscriptions
Ancient inscriptions are texts or symbols carved, engraved, or written on durable materials such as stone, metal, or clay by past civilizations, serving as primary evidence of their language, culture, beliefs, and historical events.
-
C.
epigraphic language
An epigraphic language is a language known primarily or exclusively from inscriptions carved or written on durable materials such as stone, metal, or pottery, rather than from extensive literary or manuscript traditions.
-
D.
epigrapher
An epigrapher is a specialist who studies, deciphers, and interprets inscriptions or writings engraved on durable materials such as stone, metal, or pottery to understand historical languages and cultures.
-
E.
ancient Greek inscription
An ancient Greek inscription is a text carved, painted, or otherwise permanently marked on durable materials such as stone, metal, or pottery in the Greek language, typically serving public, religious, legal, or commemorative purposes in antiquity.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:58 p.m.