Triple

T13050739
Position Surface form Disambiguated ID Type / Status
Subject Anathoth E327440 entity
Predicate associatedWithPerson P37 FINISHED
Object Abiathar E593079 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: Abiathar | Statement: [Anathoth, associatedWithPerson, Abiathar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abiathar
Context triple: [Anathoth, associatedWithPerson, Abiathar]
  • A. Abiathar chosen
    Abiathar was a high priest of ancient Israel during King David’s reign who later fell out of favor for supporting Adonijah’s unsuccessful bid for the throne.
  • B. Shaul
    Shaul is the Hebrew form of the name Saul, most famously associated with the first king of ancient Israel in the Hebrew Bible.
  • C. Shimeah
    Shimeah is a biblical figure mentioned in the Hebrew Bible, known primarily as an alternative name for Shammah.
  • D. Azariah
    Azariah is a biblical figure portrayed as one of the three youths delivered by God from the fiery furnace in the Book of Daniel and related deuterocanonical additions.
  • E. Eliashib
    Eliashib is a high priest mentioned in the Hebrew Bible during the early Second Temple period, associated with the time of Nehemiah and the rebuilding of Jerusalem’s walls.
  • 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980b98fa081908cfa92116799e874 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbda9b548190a10a4835b2c75fdc completed May 3, 2026, 4:15 a.m.
Created at: April 9, 2026, 8:57 p.m.