Triple
T25505987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadesh Treaty tablet |
E639245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | peace treaty inscription |
C50286
|
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: peace treaty inscription Context triple: [Kadesh Treaty tablet, instanceOf, peace treaty 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.
Assyrian royal inscription
An Assyrian royal inscription is a formal cuneiform text commissioned by an Assyrian king to record and glorify his military campaigns, building projects, piety, and divine legitimacy.
-
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.
Kharoṣṭhī inscription
A Kharoṣṭhī inscription is a written text carved or inscribed using the ancient Kharoṣṭhī script, primarily found on stone, metal, pottery, or other durable materials in the northwestern regions of the Indian subcontinent and Central Asia.
-
E.
ancient Greek treaty
An ancient Greek treaty is a formal, often inscribed agreement between city-states or powers that establishes terms of peace, alliance, or mutual obligations under the sanction of the gods.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:47 p.m.