Triple
T6740638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Elazar |
E154069
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Elazar |
E193643
|
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: Elazar | Statement: [David Elazar, familyName, Elazar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elazar Context triple: [David Elazar, familyName, Elazar]
-
A.
Eleazar
chosen
Eleazar is a masculine given name of Hebrew origin, traditionally associated with religious and historical figures.
-
B.
Yehuda ben Ilai
Yehuda ben Ilai was a prominent 2nd-century Tannaic sage, a leading disciple of Rabbi Akiva, and one of the most frequently cited rabbis in the Mishnah and Talmud.
-
C.
Eleazar Avaran
Eleazar Avaran was a Jewish warrior of the Maccabean revolt, renowned for his heroic death in battle against the Seleucid forces.
-
D.
Benzion
Benzion is a Hebrew masculine given name meaning "son of Zion," traditionally used in Jewish communities.
-
E.
Aharon
Aharon is a masculine given name of Hebrew origin, traditionally associated with the biblical figure Aaron and widely used in Jewish communities.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18971e081908372cd25d52a11bd |
completed | March 27, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b0fb79c8190ae9871b7b2d9d733 |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:10 p.m.