Triple

T19075914
Position Surface form Disambiguated ID Type / Status
Subject Jerubbaal E466901 entity
Predicate hasAlternativeName P39 FINISHED
Object Jerubbesheth 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: Jerubbesheth | Statement: [Jerubbaal, hasAlternativeName, Jerubbesheth]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jerubbesheth
Context triple: [Jerubbaal, hasAlternativeName, Jerubbesheth]
  • A. Cushan-Rishathaim
    Cushan-Rishathaim is a foreign king mentioned in the biblical Book of Judges as an oppressor of Israel whom God delivered into the hands of the judge Othniel.
  • B. Ish-bosheth chosen
    Ish-bosheth is a biblical figure, a son of King Saul who briefly ruled part of Israel in opposition to David after Saul’s death.
  • C. Jehozadak
    Jehozadak is a biblical priestly figure known primarily as the father of Joshua the high priest who returned with the Jewish exiles from Babylon.
  • D. Shaul
    Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
  • E. Zimri
    Zimri was a short-reigning king of the northern Kingdom of Israel, known from the Hebrew Bible for seizing the throne through a coup and then dying in a palace fire.
  • 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_69d8dd04f4488190b1121cc53ef2bfd6 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e2e49c7c8190b6ce7b918086b23c completed April 20, 2026, 8:25 a.m.
Created at: April 10, 2026, 12:04 p.m.