Triple
T2101914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uruk |
E37108
|
entity |
| Predicate | hasLegendaryKing |
P33763
|
FINISHED |
| Object | Lugalbanda |
E233594
|
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: [Uruk, hasLegendaryKing, Lugalbanda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lugalbanda Context triple: [Uruk, hasLegendaryKing, Lugalbanda]
-
A.
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.
-
B.
Eannatum
Eannatum was an early Sumerian king of Lagash known for his military conquests and one of the earliest recorded empires in Mesopotamian history.
-
C.
Naram-Sin of Akkad
Naram-Sin of Akkad was a powerful Mesopotamian king of the Akkadian Empire, famed for declaring himself a god and expanding the empire to its greatest territorial extent.
-
D.
Enmerkar
chosen
Enmerkar is a legendary Sumerian king of Uruk, best known from ancient Mesopotamian epics that depict his rivalries, quests, and early developments in writing and civilization.
-
E.
Ur-Nammu
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.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbdc11a048190ba3bbc60f90f34e1 |
completed | March 7, 2026, 5:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae518fb0b4819096a8ce455e22661a |
completed | March 9, 2026, 4:50 a.m. |
Created at: March 4, 2026, 7:43 p.m.