Triple
T20761804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillel Hassenfeld |
E510992
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Hillel |
—
|
NE NERFINISHED |
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: Hillel | Statement: [Hillel Hassenfeld, hasGivenName, Hillel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hillel Context triple: [Hillel Hassenfeld, hasGivenName, Hillel]
-
A.
Hillel
chosen
Hillel is a Hebrew given name of biblical origin commonly used in Jewish communities.
-
B.
Hillel the Elder
Hillel the Elder was a renowned 1st-century BCE–1st-century CE Jewish sage and religious leader whose teachings and interpretations of Jewish law profoundly shaped Rabbinic Judaism.
-
C.
Bar-Hillel
Bar-Hillel is a Hebrew surname most notably associated with Yehoshua Bar-Hillel, an Israeli philosopher, mathematician, and pioneer in formal linguistics and machine translation.
-
D.
Hillel II
Hillel II was a 4th-century Jewish leader best known for instituting the fixed Hebrew calendar that is still in use today.
-
E.
Shlomo Hillel
Shlomo Hillel was an Iraqi-born Israeli diplomat, politician, and key organizer of Jewish immigration from Arab countries who later held senior government roles.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2493a188190a336a35ea134e5f7 |
completed | April 21, 2026, 12:18 a.m. |
Created at: April 16, 2026, 12:35 p.m.