Triple

T15886383
Position Surface form Disambiguated ID Type / Status
Subject Beit knesset E385201 entity
Predicate relatedConcept P37 FINISHED
Object Beit din E79746 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: Beit din | Statement: [Beit knesset, relatedConcept, Beit din]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Beit din
Context triple: [Beit knesset, relatedConcept, Beit din]
  • A. Beit din chosen
    Beit din is a rabbinical court in Judaism that adjudicates matters of religious law, personal status, and communal disputes.
  • B. Beit
    Beit is a surname most notably associated with Alfred Beit, a prominent 19th-century British-German businessman and philanthropist involved in diamond and gold mining in South Africa.
  • C. Beit Wing
    Beit Wing is a major gallery space within the National Gallery of Ireland that houses part of its art collection and exhibitions.
  • D. Beit Furik
    Beit Furik is a Palestinian town in the Nablus area of the northern West Bank, known for its agricultural landscape and traditional rural character.
  • E. Beit Yosef
    Beit Yosef is a comprehensive halachic commentary on the Arba'ah Turim by Rabbi Yosef Karo, serving as the primary source and foundation for his later code, the Shulchan Aruch.
  • 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_69e1561a68d8819099e60e2f1f0db07a completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa95791a48190abc79a6906672098 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.