Triple

T4768244
Position Surface form Disambiguated ID Type / Status
Subject Huldah E105863 entity
Predicate associatedWith P37 FINISHED
Object High Priest Hilkiah E327441 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: High Priest Hilkiah | Statement: [Huldah, associatedWith, High Priest Hilkiah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: High Priest Hilkiah
Context triple: [Huldah, associatedWith, High Priest Hilkiah]
  • A. Hilkiah chosen
    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.
  • B. Mattaniah
    Mattaniah is the birth name of the last king of Judah, later renamed Zedekiah by the Babylonian king Nebuchadnezzar.
  • C. Zerubbabel
    Zerubbabel was a Jewish leader and governor of Judah under Persian rule who oversaw the rebuilding of the Second Temple in Jerusalem after the Babylonian exile.
  • D. Nahum King
    Nahum King was an early settler and prominent local figure after whom the community of Kings Valley, Oregon, was named.
  • E. Yehoyaqim
    Yehoyaqim is a king of Judah mentioned in the Hebrew Bible, known for his reign during the late 7th to early 6th century BCE amid rising Babylonian power.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6537eb80819096e0ae906c59d605 completed March 20, 2026, 3:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a8f7318819088839becd09577ce completed March 21, 2026, 6:28 a.m.
Created at: March 20, 2026, 1:21 p.m.