Triple

T4838740
Position Surface form Disambiguated ID Type / Status
Subject Hezekiah E108127 entity
Predicate father P120 FINISHED
Object Ahaz E474798 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: Ahaz | Statement: [Hezekiah, father, Ahaz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ahaz
Context triple: [Hezekiah, father, Ahaz]
  • A. Ahaz chosen
    Ahaz was a king of Judah in the Hebrew Bible, known for his unfaithfulness to God and political alliances with Assyria.
  • B. Hezekiah
    Hezekiah was a king of Judah in the Hebrew Bible, remembered for his religious reforms, resistance to Assyrian invasion, and reliance on prophetic counsel.
  • C. 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.
  • D. Uzziah
    Uzziah was a long-reigning king of Judah in the Hebrew Bible, remembered for his military success, economic prosperity, and eventual downfall after being struck with leprosy.
  • E. Manasseh
    Manasseh is one of the tribes of Israel, traditionally descended from Joseph’s son Manasseh and associated with territory on both sides of the Jordan River.
  • 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_69bd43fbe444819085cb970706ef73f7 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6ce4a5108190aede620d5dde1f81 completed March 20, 2026, 3:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69be67d449188190a2f02fa30aee4891 completed March 21, 2026, 9:41 a.m.
Created at: March 20, 2026, 1:25 p.m.