Triple
T5934998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belšar-uṣur |
E132021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Neo-Babylonian prince |
C19602
|
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: Neo-Babylonian prince Context triple: [Belšar-uṣur, instanceOf, Neo-Babylonian prince]
-
A.
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.
-
B.
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.
-
C.
Jewish prince
A Jewish prince is a noble or royal figure of Jewish heritage, often positioned at the intersection of religious tradition, cultural identity, and political authority.
-
D.
regent of the Seleucid Empire
A regent of the Seleucid Empire is an individual who temporarily governed the Hellenistic Seleucid state on behalf of an underage, absent, or otherwise incapacitated king, exercising royal authority without holding the full royal title.
-
E.
Nabataean king
A Nabataean king is the sovereign ruler of the ancient Nabataean kingdom, overseeing its political, military, economic, and religious affairs from its capital at Petra and other regional centers.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.