Triple

T208044
Position Surface form Disambiguated ID Type / Status
Subject Hebrew E4650 entity
Predicate usedInText P907 FINISHED
Object Mishnah E8388 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: Mishnah | Statement: [Hebrew, usedInText, Mishnah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mishnah
Context triple: [Hebrew, usedInText, Mishnah]
  • A. Mishnah chosen
    The Mishnah is the foundational written compilation of Jewish oral law that underpins the Talmud and later rabbinic legal tradition.
  • B. Talmud
    The Talmud is a central Jewish religious text comprising rabbinic discussions, legal rulings, and interpretations of the Hebrew Bible that form the foundation of traditional Jewish law and theology.
  • C. Arba’ah Turim
    Arba’ah Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes and clarifies halakhic rulings for practical religious life.
  • D. Mishneh Torah
    Mishneh Torah is a comprehensive 12th-century Jewish legal code by Maimonides that systematically organizes and clarifies all of Jewish law.
  • E. Shulchan Aruch
    Shulchan Aruch is a seminal 16th-century codification of Jewish law that serves as the primary halachic reference for much of the Jewish world.
  • 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_69a25737567c81908f9c505300239181 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a260c178ac819085eb94ccaf64b780 completed Feb. 28, 2026, 3:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69a36ceeaf6081908056040506197a18 completed Feb. 28, 2026, 10:32 p.m.
Created at: Feb. 28, 2026, 2:51 a.m.