Triple
T30163770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesilim |
E766738
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Mesopotamian ruler |
C35847
|
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: ancient Mesopotamian ruler Context triple: [Mesilim, instanceOf, ancient Mesopotamian ruler]
-
A.
ancient Near Eastern ruler
An ancient Near Eastern ruler is a sovereign leader who governed a city-state or empire in regions such as Mesopotamia, Anatolia, the Levant, or Persia, wielding political, military, economic, and often religious authority.
-
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.
Suebian king
A Suebian king is the sovereign ruler of the ancient Germanic Suebi people, exercising military, judicial, and political authority over their tribal confederation.
-
D.
Amorite king
chosen
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.
-
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.
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:22 p.m.