Triple

T19837573
Position Surface form Disambiguated ID Type / Status
Subject Malchi-shua son of Saul E476637 entity
Predicate sibling P363 FINISHED
Object Abinadab son of Saul 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: Abinadab son of Saul | Statement: [Malchi-shua son of Saul, sibling, Abinadab son of Saul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abinadab son of Saul
Context triple: [Malchi-shua son of Saul, sibling, Abinadab son of Saul]
  • A. Abinadab chosen
    Abinadab is a son of King Saul mentioned in the Hebrew Bible, known for dying alongside his father in battle against the Philistines.
  • B. Abinadab
    Abinadab is a biblical figure mentioned in the Old Testament as one of King David’s brothers and a son of Jesse of Bethlehem.
  • C. Shaul
    Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
  • D. Abinoam
    Abinoam is a biblical figure mentioned in the Old Testament as the father of the Israelite military leader Barak.
  • E. Barzillai the Gileadite
    Barzillai the Gileadite is a wealthy, elderly supporter of King David in the Hebrew Bible who loyally aided him during his flight from Absalom.
  • 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_69d8e51d39d081909bcfafeaaf3d2fcc completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65802f57081909e4e94694684bda4 completed April 20, 2026, 4:44 p.m.
Created at: April 10, 2026, 1:50 p.m.