Triple

T2488066
Position Surface form Disambiguated ID Type / Status
Subject Mapah E55974 entity
Predicate legalDomain P1248 FINISHED
Object Orach Chaim E148752 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: Orach Chaim | Statement: [Mapah, legalDomain, Orach Chaim]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orach Chaim
Context triple: [Mapah, legalDomain, Orach Chaim]
  • A. Orach Chayim chosen
    Orach Chayim is a section of Jewish law that primarily deals with daily religious practices, prayer, Shabbat, and festivals.
  • B. Seder Zeraim
    Seder Zeraim is the first order of the Mishnah, primarily dealing with agricultural laws and blessings in Jewish law.
  • C. Hoshanot
    Hoshanot are a series of liturgical supplications recited while circling the synagogue with lulav and etrog during Sukkot, beseeching divine salvation and blessing.
  • D. Salo
    Salo is a town in southwestern Finland known for its electronics industry history and location along the Salo River.
  • E. Malchi-shua
    Malchi-shua was one of King Saul’s sons, a Hebrew prince mentioned in the Bible who died alongside his father in battle against the Philistines.
  • 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_69ab49e670a88190b928e08302381710 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd179c44881909cd6c7626cadaf10 completed March 7, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69af17bca6f88190a63672fb3372f0be completed March 9, 2026, 6:55 p.m.
Created at: March 6, 2026, 9:45 p.m.