Triple

T4012445
Position Surface form Disambiguated ID Type / Status
Subject Alexander Jannaeus E90676 entity
Predicate alsoKnownAs P39 FINISHED
Object Yehonatan E225874 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: Yehonatan | Statement: [Alexander Jannaeus, alsoKnownAs, Yehonatan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yehonatan
Context triple: [Alexander Jannaeus, alsoKnownAs, Yehonatan]
  • A. Yonatan chosen
    Yonatan is a Hebrew given name, commonly associated with the biblical figure Jonathan and meaning "God has given."
  • B. Yehuda
    Yehuda is a Hebrew given name traditionally associated with the biblical tribe of Judah and commonly used in Jewish communities.
  • C. Natan
    Natan is a masculine given name of Hebrew origin, commonly used in Jewish and Israeli communities and meaning "he gave."
  • D. Or Yehuda
    Or Yehuda is a city in central Israel, located in the Tel Aviv District and functioning largely as a residential suburb of the Tel Aviv metropolitan area.
  • E. Zimran
    Zimran is a lesser-known biblical figure mentioned in the Hebrew Bible as one of Abraham's sons by his wife Keturah.
  • 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_69aed95e44088190aff7d90a151b1b20 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa893ce08190b8fe49a11123738d completed March 9, 2026, 4:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54c70eb7c8190bc5c4086b756c9c4 completed March 14, 2026, 11:54 a.m.
Created at: March 9, 2026, 3:34 p.m.