Triple
T31881986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachish Letters |
E813906
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inscribed ostraca collection |
C18119
|
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: inscribed ostraca collection Context triple: [Lachish Letters, instanceOf, inscribed ostraca collection]
-
A.
Aramaic papyri
Aramaic papyri are ancient documents written in the Aramaic language on papyrus, typically comprising letters, legal contracts, and administrative records that illuminate the social, economic, and political life of Near Eastern communities.
-
B.
cuneiform tablets collection
A cuneiform tablets collection is an organized assemblage of inscribed clay tablets that preserves and categorizes ancient written records for study, interpretation, and cultural heritage.
-
C.
Proto-Canaanite inscription
A Proto-Canaanite inscription is an early alphabetic text, typically carved on stone or pottery in the Levant during the late second millennium BCE, representing one of the earliest known stages of the Canaanite (and thus later Phoenician and Hebrew) writing system.
-
D.
ancient inscriptions
chosen
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.
-
E.
mosaic inscription
A mosaic inscription is a text or message formed by arranging small, colored pieces of stone, glass, or tile within a mosaic design, typically serving decorative, commemorative, or religious purposes.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:56 p.m.