Triple
T8925538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lagash |
E212531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Sumerian city-state |
C9491
|
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 Sumerian city-state Context triple: [Lagash, instanceOf, ancient Sumerian city-state]
-
A.
Mesopotamian city
chosen
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 Egyptian city
An ancient Egyptian city is an urban settlement along the Nile characterized by monumental temples and tombs, administrative and residential districts, and a society organized around pharaonic rule, religion, and agriculture.
-
D.
Sumerian artifact
A Sumerian artifact is a physical object created or used by the ancient Sumerian civilization that reflects their daily life, beliefs, technology, or artistic expression.
-
E.
pre-Columbian city-state
A pre-Columbian city-state is an autonomous urban-centered political entity in the Americas that existed before European contact, typically comprising a primary city and its surrounding territories, governed by its own ruling elite, institutions, and cultural traditions.
- 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.