Triple

T19880508
Position Surface form Disambiguated ID Type / Status
Subject Manishtushu E477755 entity
Predicate sibling P363 FINISHED
Object Rimush 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: Rimush | Statement: [Manishtushu, sibling, Rimush]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rimush
Context triple: [Manishtushu, sibling, 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. Hushim
    Hushim is a minor biblical figure mentioned in the Hebrew Bible as a descendant of Jacob through his son Dan.
  • D. Tash-Murkon
    Tash-Murkon is a prominent and wealthy region of the Amarr Empire in the EVE Online universe, known for its powerful royal house and extensive trade activity.
  • E. Romm
    Romm is a surname most notably associated with Soviet film director and screenwriter Mikhail Romm.
  • 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.