Triple
T9071204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashur-uballit I |
E217369
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Assyrian king |
C13119
|
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: Assyrian king Context triple: [Ashur-uballit I, instanceOf, Assyrian king]
-
A.
Neo-Assyrian king
chosen
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.
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.
-
D.
Kayanian king
A Kayanian king is the sovereign ruler of the ancient Kayanian dynasty, embodying divine authority, martial prowess, and the cultural ideals of his realm.
-
E.
Sasanian king
A Sasanian king is the sovereign ruler of the Sasanian Empire, wielding supreme political, military, and religious authority over its territories and subjects.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:12 p.m.