Triple
T15837613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashur-nirari V |
E384023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | king of Assyria |
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: king of Assyria Context triple: [Ashur-nirari V, instanceOf, king of Assyria]
-
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.
King of Urartu
The King of Urartu is the sovereign ruler of the ancient kingdom of Urartu, responsible for governing its territories, commanding its military, overseeing religious and administrative affairs, and representing the state in foreign relations.
-
C.
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.
-
D.
king of Lydia
A king of Lydia is the sovereign ruler of the ancient Anatolian kingdom of Lydia, holding supreme political, military, and religious authority over its people and territories.
-
E.
Assyrian dynasty
An Assyrian dynasty is a ruling lineage or succession of kings that governed the Assyrian state or empire during a distinct historical period in ancient Mesopotamia.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.