Triple
T22070499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Service |
E545391
|
entity |
| Predicate | relatedWorkByComposer |
P30528
|
FINISHED |
| Object | Baal Shem |
—
|
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: Baal Shem | Statement: [Sacred Service, relatedWorkByComposer, Baal Shem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baal Shem Context triple: [Sacred Service, relatedWorkByComposer, Baal Shem]
-
A.
Baal Shem
chosen
Baal Shem is a three-movement suite for violin and orchestra (or piano) by composer Ernest Bloch, inspired by Jewish liturgical and folk traditions.
-
B.
Baal Shem Tov
Baal Shem Tov was an 18th-century Jewish mystic and spiritual leader regarded as the founder of the Hasidic movement.
-
C.
Dov Ber of Mezeritch
Dov Ber of Mezeritch was an 18th-century Hasidic master and successor to the Baal Shem Tov, renowned for systematizing and spreading early Hasidic thought across Eastern Europe.
-
D.
Yisrael ben Eliezer
Yisrael ben Eliezer, known as the Baal Shem Tov, was an 18th-century Jewish mystic and healer who founded the Hasidic movement in Eastern Europe.
-
E.
Nachman
Nachman is a masculine given name of Hebrew origin, traditionally used in Jewish communities.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128881af481909b28cda2d343f4e3 |
completed | April 28, 2026, 9:37 p.m. |
Created at: April 16, 2026, 8:28 p.m.