Triple
T14475646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabu-balatsu-iqbi |
E358963
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Babylonian nobleman |
C34826
|
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: Babylonian nobleman Context triple: [Nabu-balatsu-iqbi, instanceOf, Babylonian nobleman]
-
A.
Neo-Babylonian prince
A Neo-Babylonian prince is a royal male heir or close relative of the king in the Neo-Babylonian Empire (c. 626–539 BCE), raised within the courtly, military, and religious traditions that prepared him for governance and dynastic continuity.
-
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.
Assyrian general
An Assyrian general is a high-ranking military commander in the ancient Assyrian Empire responsible for planning campaigns, leading armies in battle, and enforcing the king’s authority through warfare and conquest.
-
D.
Babylonian scholar
A Babylonian scholar is an educated individual in ancient Mesopotamia who studies, preserves, and interprets knowledge in fields such as astronomy, mathematics, divination, and literature, often serving in temples or royal courts.
-
E.
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.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:20 a.m.