Triple
T13317537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naftali Bennett |
E317226
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Naftali |
E722193
|
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: Naftali | Statement: [Naftali Bennett, givenName, Naftali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Naftali Context triple: [Naftali Bennett, givenName, Naftali]
-
A.
Naftali
chosen
Naftali is a Hebrew given name historically borne by notable Jewish figures, including poets and religious leaders.
-
B.
Natan
Natan is a masculine given name of Hebrew origin, commonly used in Jewish and Israeli communities and meaning "he gave."
-
C.
Yonatan
Yonatan is a Hebrew given name, commonly associated with the biblical figure Jonathan and meaning "God has given."
-
D.
Yair
Yair is a masculine given name of Hebrew origin, commonly used in Israel and among Jewish communities worldwide.
-
E.
Nethanel
Nethanel is a biblical figure mentioned as one of the sons in Jesse’s family line, associated with the ancestry of King David.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990f9a384819085890e18255ee339 |
completed | April 11, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716ee695c81909ffeeb0901ee66c1 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:29 p.m.