Triple
T3874400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talang Tuwo inscription |
E92463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 7th-century inscription |
C14247
|
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: 7th-century inscription Context triple: [Talang Tuwo inscription, instanceOf, 7th-century 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.
Oscan inscription
An Oscan inscription is a written text in the Oscan language, typically carved on stone, metal, or pottery by ancient Italic peoples, providing evidence of their language, culture, and public or religious life.
-
C.
Etruscan inscription
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.
-
D.
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.
-
E.
5th-century text
A 5th-century text is a written work created or compiled between 401 and 500 CE, reflecting the linguistic, cultural, religious, and intellectual contexts of that historical period.
- 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.