Triple

T3976917
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Judah E85664 entity
Predicate notableKing P6811 FINISHED
Object Hezekiah E108127 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: Hezekiah | Statement: [Kingdom of Judah, notableKing, Hezekiah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hezekiah
Context triple: [Kingdom of Judah, notableKing, Hezekiah]
  • A. Hezekiah chosen
    Hezekiah was a king of Judah in the Hebrew Bible, remembered for his religious reforms, resistance to Assyrian invasion, and reliance on prophetic counsel.
  • B. Pekah
    Pekah was a king of the northern Kingdom of Israel in the 8th century BCE, known for his reign during a period of political instability and conflict with Assyria.
  • C. Hoshea
    Hoshea was the last king of the northern Kingdom of Israel, whose reign ended with the Assyrian conquest and the kingdom’s destruction in the 8th century BCE.
  • D. Jekonias
    Jekonias is an alternate name for Jehoiachin, a king of Judah mentioned in the Hebrew Bible and Old Testament.
  • E. 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.
  • 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_69aed93908348190a26c8aaf4fab3e86 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef9b876d8819082f4b81c9699913a completed March 9, 2026, 4:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5401ac15481908ab86c8ef48ce413 completed March 14, 2026, 11:01 a.m.
Created at: March 9, 2026, 3:33 p.m.