Triple

T19081826
Position Surface form Disambiguated ID Type / Status
Subject Ahikam son of Shaphan E467049 entity
Predicate family P566 FINISHED
Object Gemariah son of Shaphan NE NERFINISHED

How this triple was built (3 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: Gemariah son of Shaphan | Statement: [Ahikam son of Shaphan, family, Gemariah son of Shaphan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gemariah son of Shaphan
Context triple: [Ahikam son of Shaphan, family, Gemariah son of Shaphan]
  • A. Ahikam son of Shaphan
    Ahikam son of Shaphan was a Judean official and supporter of the prophet Jeremiah who helped protect him and played a key role in the religious reforms during King Josiah’s reign.
  • B. Shaphan the scribe
    Shaphan the scribe was a royal secretary in the Hebrew Bible who served King Josiah and played a key role in the discovery and reading of the Book of the Law during the temple repairs.
  • C. Azariah the priest
    Azariah the priest was a high priest in ancient Judah, noted in the Bible for courageously confronting King Uzziah when the king unlawfully attempted to burn incense in the temple.
  • D. Hilkiah
    Hilkiah is a biblical figure known as the father of the prophet Jeremiah and, in some traditions, identified with the high priest who discovered the Book of the Law in the Temple.
  • E. Shemaiah
    Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Gemariah son of Shaphan
Target entity description: Gemariah son of Shaphan is a biblical figure mentioned in the Book of Jeremiah, known as one of Shaphan the scribe’s sons who was involved in events surrounding the prophet’s scroll.
  • A. Ahikam son of Shaphan
    Ahikam son of Shaphan was a Judean official and supporter of the prophet Jeremiah who helped protect him and played a key role in the religious reforms during King Josiah’s reign.
  • B. Shaphan the scribe
    Shaphan the scribe was a royal secretary in the Hebrew Bible who served King Josiah and played a key role in the discovery and reading of the Book of the Law during the temple repairs.
  • C. Azariah the priest
    Azariah the priest was a high priest in ancient Judah, noted in the Bible for courageously confronting King Uzziah when the king unlawfully attempted to burn incense in the temple.
  • D. Hilkiah
    Hilkiah is a biblical figure known as the father of the prophet Jeremiah and, in some traditions, identified with the high priest who discovered the Book of the Law in the Temple.
  • E. Shemaiah
    Shemaiah is a biblical figure known primarily as the father of Uriah mentioned in the Hebrew Bible.
  • F. None of above. chosen

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_69e5e2e9fccc819092c06c5da6f043ac completed April 20, 2026, 8:25 a.m.
Created at: April 10, 2026, 12:04 p.m.