Triple

T6346554
Position Surface form Disambiguated ID Type / Status
Subject Israel ben Eliezer E142757 entity
Predicate hasTitle P38 FINISHED
Object Baal Shem E546754 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: Baal Shem | Statement: [Israel ben Eliezer, hasTitle, Baal Shem]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Baal Shem
Context triple: [Israel ben Eliezer, hasTitle, 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 (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_69c008d5ab108190b346c465696824a9 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c067b907c4819085a3ea87589bc4be completed March 22, 2026, 10:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69c66376b63081909fefd93790fa4b55 completed March 27, 2026, 11:01 a.m.
Created at: March 22, 2026, 4:31 p.m.