Triple
T6343658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesha Stele |
E142692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Moabite inscription |
C20219
|
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: Moabite inscription Context triple: [Mesha Stele, instanceOf, Moabite inscription]
-
A.
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.
-
B.
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.
-
C.
Srivijayan inscription
A Srivijayan inscription is an ancient written record, typically carved in stone or metal, produced under the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
D.
Srivijaya inscription
A Srivijaya inscription is an ancient written record, typically in Old Malay or Sanskrit, produced by the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
E.
Assyrian palace reliefs
Assyrian palace reliefs are intricately carved stone panels that decorated royal Assyrian palaces, depicting military campaigns, hunting scenes, religious rituals, and courtly life to glorify the king’s power and divine authority.
- 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:31 p.m.