Triple
T15892036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moyshe-Leyb Halpern |
E385349
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Halpern |
E1170354
|
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: Halpern | Statement: [Moyshe-Leyb Halpern, familyName, Halpern]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Halpern Context triple: [Moyshe-Leyb Halpern, familyName, Halpern]
-
A.
Halpern
chosen
Halpern is a Jewish surname of Ashkenazi origin borne by various notable figures, including writers such as H. Leivick.
-
B.
Parnes
Parnes is a mountain in Greece traditionally associated with the ancient Greek personifications of mountains known as the Ourea.
-
C.
Herlihy
Herlihy is an Irish-origin surname borne by various notable individuals, including writers, scholars, and public figures.
-
D.
Pfefferberg
Pfefferberg is a surname most notably associated with Poldek Pfefferberg, a Holocaust survivor who played a key role in bringing Oskar Schindler’s story to public attention.
-
E.
Kuppenheimer
Kuppenheimer was a prominent American men's clothing company best known for its high-quality suits and influential early 20th-century advertising campaigns.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561f515081908ba4e68e1347a881 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb047b6248190b6c11ef20636f50f |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:51 a.m.