Triple
T9256548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sargon of Akkad |
E222456
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Rimush |
E477754
|
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: Rimush | Statement: [Sargon of Akkad, successor, Rimush]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rimush Context triple: [Sargon of Akkad, successor, Rimush]
-
A.
Rimush
chosen
Rimush was an Akkadian king of the 23rd century BCE, known for consolidating and brutally defending the empire established by his father, Sargon of Akkad.
-
B.
Rakhumai
Rakhumai is a revered Hindu goddess worshipped as the compassionate consort of Vithoba (a form of Krishna/Vishnu) at the famous Pandharpur temple in Maharashtra.
-
C.
Romm
Romm is a surname most notably associated with Soviet film director and screenwriter Mikhail Romm.
-
D.
Tumshuq
Tumshuq is an ancient city in the Tarim Basin region of Xinjiang, China, historically associated with the Saka (Scythian) peoples and their Eastern Iranian languages.
-
E.
Morshi
Morshi is a town in the Amravati district of Maharashtra, India, known primarily as an agricultural and local trading center.
- 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_69ca841e4cd481908e738c74e958eaea |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd06b4e2048190af0d65b904677c36 |
completed | April 1, 2026, 11:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d09be75fd88190b6e99b0884dcc14c |
completed | April 4, 2026, 5:04 a.m. |
Created at: March 30, 2026, 7:32 p.m.