Triple
T30482571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shalmaneser I |
E775624
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Assyrian king |
C57059
|
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: Middle Assyrian king Context triple: [Shalmaneser I, instanceOf, Middle Assyrian king]
-
A.
Neo-Assyrian king
A Neo-Assyrian king is the supreme monarch of the Neo-Assyrian Empire, wielding absolute political, military, and religious authority to expand and maintain imperial power across the ancient Near East.
-
B.
Neo-Babylonian king
A Neo-Babylonian king is the sovereign ruler of the Neo-Babylonian Empire (c. 626–539 BCE), responsible for military leadership, monumental building projects, religious patronage, and the administration of law and tribute across Mesopotamia.
-
C.
Amorite king
An Amorite king is a Bronze Age ruler from the Amorite people of ancient Mesopotamia, governing city-states or kingdoms such as Babylon through military power, diplomacy, and religious authority.
-
D.
Hittite king
A Hittite king is the supreme political, military, and religious ruler of the Hittite Empire, responsible for governing the state, leading armies, conducting diplomacy, and performing key religious rituals to maintain divine favor and social order.
-
E.
Assyrian prince
An Assyrian prince is a high-ranking male member of the royal family in ancient Assyria, often groomed for leadership, military command, and the administration of the empire’s territories.
- 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:13 p.m.