Triple
T8926149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ur III dynasty |
E212542
|
entity |
| Predicate | foundedBy |
P104
|
FINISHED |
| Object | Ur-Nammu |
E212538
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ur-Nammu | Statement: [Ur III dynasty, foundedBy, Ur-Nammu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ur-Nammu Context triple: [Ur III dynasty, foundedBy, Ur-Nammu]
-
A.
Ur-Nammu
chosen
Ur-Nammu was an ancient Sumerian king of Ur best known for founding the Third Dynasty of Ur and issuing one of the earliest known law codes in history.
-
B.
Lugalzagesi
Lugalzagesi was a Sumerian king of Umma and later ruler of a briefly unified Sumer, known for his military conquests and eventual defeat by Sargon of Akkad.
-
C.
Ur-Nammur
Ur-Nammur is an alternate spelling of Ur-Nammu, the Sumerian king of Ur who founded the Third Dynasty of Ur and issued one of the earliest known law codes.
-
D.
Lugal Kish
Lugal Kish is an ancient Mesopotamian royal title denoting the king or ruler of the city-state of Kish, often associated with early Sumerian hegemony.
-
E.
Eannatum
Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69cc66700fb48190874563e535f20437 |
completed | April 1, 2026, 12:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1af0f42488190a298eb449828b9ae |
completed | April 5, 2026, 12:38 a.m. |
Created at: March 30, 2026, 6:57 p.m.