Triple
T2016607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan |
E44008
|
entity |
| Predicate | cognate |
P2527
|
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: [Jonathan, cognate, Yehonatan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yehonatan Context triple: [Jonathan, cognate, Yehonatan]
-
A.
Yonatan
chosen
Yonatan is a Hebrew given name, commonly associated with the biblical figure Jonathan and meaning "God has given."
-
B.
Zimran
Zimran is a lesser-known biblical figure mentioned in the Hebrew Bible as one of Abraham's sons by his wife Keturah.
-
C.
Shlomo
Shlomo is the Hebrew name for King Solomon, the biblical monarch renowned for his wisdom, wealth, and the construction of the First Temple in Jerusalem.
-
D.
Ze'ev
Ze'ev is a Hebrew given name meaning "wolf," commonly used in Israel and among Jewish communities worldwide.
-
E.
Ehud
Ehud is a biblical judge and deliverer of Israel known for assassinating the Moabite king Eglon in the Book of Judges.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ccdb7c81909f6b3c96f79fcdfc |
completed | March 7, 2026, 5:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae270a8cd88190a17839c345424ccd |
completed | March 9, 2026, 1:48 a.m. |
Created at: March 4, 2026, 7:38 p.m.