Triple
T31149112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lugal Kish |
E794018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Mesopotamian title |
C14181
|
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: ancient Mesopotamian title Context triple: [Lugal Kish, instanceOf, ancient Mesopotamian title]
-
A.
Mesopotamian royal epithet
chosen
A Mesopotamian royal epithet is a formal, often formulaic honorific phrase used in inscriptions and texts to define, praise, and legitimize a king’s divine favor, authority, and achievements.
-
B.
ancient Egyptian royal title
An ancient Egyptian royal title is a formal designation used to identify and legitimize a pharaoh or member of the royal family, often reflecting divine authority, political power, and religious roles within the kingdom.
-
C.
ancient South Arabian title
An ancient South Arabian title is a formal designation or rank used in the inscriptions and administrative records of ancient South Arabian civilizations to denote social, political, or religious status.
-
D.
Nubian title
A Nubian title is an honorific or official designation used in ancient Nubian societies to denote social rank, political authority, religious office, or royal status within their hierarchical structure.
-
E.
Mycenaean title
A Mycenaean title is an official designation or rank recorded in Linear B script that identifies the social, administrative, or religious role of an individual within Mycenaean society.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:06 p.m.