Triple
T19880455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rimush |
E477754
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | King of Kish |
—
|
NE NERFINISHED |
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 Kish | Statement: [Rimush, title, King of Kish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King of Kish Context triple: [Rimush, title, King of Kish]
-
A.
Sargon
Sargon is the main antagonist, a ruthless and power-hungry warrior, in the fantasy action film "The Scorpion King 2: Rise of a Warrior."
-
B.
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.
-
C.
Sargon of Akkad
Sargon of Akkad was an ancient Mesopotamian king who founded the Akkadian Empire, often regarded as the world’s first great empire.
-
D.
Lugal Kish
chosen
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.
Lugalanda
Lugalanda was an early Sumerian ruler of the city-state of Lagash, known from cuneiform inscriptions dating to the mid-3rd millennium BCE.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658de4b288190a41bee67f570be1e |
completed | April 20, 2026, 4:48 p.m. |
Created at: April 10, 2026, 1:52 p.m.