Triple
T1985335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cippus Abellanus |
E43126
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient stone inscription |
C6921
|
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: ancient stone inscription Context triple: [Cippus Abellanus, instanceOf, ancient stone inscription]
-
A.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
B.
Etruscan inscription
chosen
An Etruscan inscription is a text written in the ancient Etruscan language, typically carved or painted on durable materials such as stone, metal, or pottery, providing evidence of the culture, religion, and daily life of the Etruscan civilization.
-
C.
Latin inscription
A Latin inscription is a text carved, engraved, or otherwise permanently marked in the Latin language on durable materials such as stone, metal, or pottery, typically serving commemorative, dedicatory, legal, or informational purposes.
-
D.
inscription corpus
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.
-
E.
ancient Roman monument
An ancient Roman monument is a large, enduring structure or commemorative work built by the Romans to honor deities, leaders, victories, or civic achievements, often showcasing advanced engineering and classical architectural styles.
- 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_69a88713ddc88190a969715658ebe7a8 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.