Triple
T9661280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enmerkar |
E233594
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Lugalbanda |
E796988
|
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: Lugalbanda | Statement: [Enmerkar, successor, Lugalbanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lugalbanda Context triple: [Enmerkar, successor, Lugalbanda]
-
A.
Lugalbanda
chosen
Lugalbanda is a heroic king of Uruk from Sumerian mythology, known both as a central figure in early epic tales and as the father of the legendary hero Gilgamesh.
-
B.
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.
-
C.
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.
-
D.
Eannatum
Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
-
E.
Urukagina
Urukagina was a Sumerian ruler of the city-state of Lagash, known for instituting some of the earliest recorded social and legal reforms in 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0a15e4819092ea0fb2cb6e1c12 |
completed | April 1, 2026, 10:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d25743261881909b207405d5eaa4cd |
completed | April 5, 2026, 12:36 p.m. |
Created at: March 30, 2026, 8:14 p.m.