Triple
T6936194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachish ewer inscription |
E160559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Proto-Canaanite inscription |
C21372
|
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: Proto-Canaanite inscription Context triple: [Lachish ewer inscription, instanceOf, Proto-Canaanite inscription]
-
A.
Moabite inscription
A Moabite inscription is an ancient text carved in the Moabite language, typically on stone or other durable materials, that records historical, religious, or political information from the Iron Age kingdom of Moab.
-
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.
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.
-
D.
cuneiform script
Cuneiform script is one of the earliest known systems of writing, developed by the ancient Sumerians of Mesopotamia, characterized by wedge-shaped marks impressed on clay tablets.
-
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. 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:27 p.m.