Triple
T10359828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amar-Sin |
E244103
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | King of Ur |
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: King of Ur | Statement: [Amar-Sin, title, King of Ur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King of Ur Context triple: [Amar-Sin, title, King of Ur]
-
A.
Lord of Ur
Lord of Ur is an epithet of the Mesopotamian moon god Nanna (also known as Sin), highlighting his role as the chief deity and divine patron of the ancient city of Ur.
-
B.
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.
-
C.
Lugalanda
Lugalanda was an early Sumerian ruler of the city-state of Lagash, known from cuneiform inscriptions dating to the mid-3rd millennium BCE.
-
D.
Gugalanna
Gugalanna is a Sumerian deity known as the Bull of Heaven, associated with the sky and sent by the gods as a destructive force in Mesopotamian mythology.
-
E.
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.
- 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9609c4481908b7d72ecf1adaa73 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d750b6ef248190bdbe16bbb8efcf88 |
completed | April 9, 2026, 7:09 a.m. |
Created at: April 6, 2026, 11:59 a.m.