Triple
T8926164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Babylonian Empire |
E212543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Mesopotamian state |
C4291
|
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 state Context triple: [Old Babylonian Empire, instanceOf, ancient Mesopotamian state]
-
A.
Mesopotamian city
A Mesopotamian city is an ancient urban settlement characterized by organized streets, monumental temples (ziggurats), centralized administration, and irrigation-based agriculture along the Tigris and Euphrates rivers.
-
B.
Canaanite city-state
A Canaanite city-state is an independent, fortified urban center in ancient Canaan that controlled its surrounding territory, governed by a local ruler and integrated into regional trade, diplomacy, and warfare.
-
C.
ancient Chinese state
An ancient Chinese state is a historically documented political entity that existed within the territory of what is now China, characterized by its own ruling house, administrative system, culture, and military, and interacting with neighboring states through warfare, diplomacy, and trade.
-
D.
Semitic state
A Semitic state is a political entity historically or culturally rooted in Semitic-speaking peoples, characterized by shared linguistic, ethnic, and often religious traditions originating in the ancient Near East.
-
E.
ancient kingdom
chosen
An ancient kingdom is a historically early, centralized state ruled by a monarch, characterized by hierarchical social structures, distinct cultural traditions, and control over defined territories.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.