Triple
T30588532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isin-Larsa period |
E778584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mesopotamian historical period |
C25298
|
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: Mesopotamian historical period Context triple: [Isin-Larsa period, instanceOf, Mesopotamian historical period]
-
A.
Mesopotamian period
chosen
The Mesopotamian period refers to the ancient era in the region between the Tigris and Euphrates rivers, marked by the rise of early urban civilizations, writing systems, and complex social, political, and religious structures.
-
B.
Anatolian historical period
The Anatolian historical period encompasses the succession of ancient and medieval eras in the region of Anatolia (Asia Minor), marked by the rise and interaction of civilizations such as the Hittites, Phrygians, Lydians, Greeks, Persians, Romans, Byzantines, and early Turks.
-
C.
Sumerian dynasty
A Sumerian dynasty is a succession of rulers from the same family or lineage who governed a Sumerian city-state or region in ancient Mesopotamia.
-
D.
ancient Near Eastern dynasty
An ancient Near Eastern dynasty is a succession of rulers from the same family or lineage that governed a state or empire in the Near East during antiquity, shaping its political, cultural, and religious development over time.
-
E.
period of ancient Egypt
A period of ancient Egypt is a distinct span of time in Egyptian history characterized by specific political structures, cultural developments, dynastic rule, and major events that differentiate it from other eras.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:24 p.m.