Triple

T113135
Position Surface form Disambiguated ID Type / Status
Subject Rosh Hashanah E2287 entity
Predicate workRestriction P1050 FINISHED
Object considered a Yom Tov with prohibited forms of work LITERAL 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: considered a Yom Tov with prohibited forms of work | Statement: [Rosh Hashanah, workRestriction, considered a Yom Tov with prohibited forms of work]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: workRestriction
Context triple: [Rosh Hashanah, workRestriction, considered a Yom Tov with prohibited forms of work]
  • A. worksWith
    Indicates that two entities collaborate or perform tasks together in a shared work-related context.
  • B. restriction chosen
    Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
  • C. locationOfWork
    Indicates the place or site where an entity performs its work or carries out its professional activities.
  • D. limitsOffice
    Indicates that one entity imposes a restriction or cap on the scope, duration, or powers of another entity’s office or official position.
  • E. laborSystem
    Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
  • F. None of above.

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_69a24fcdaeb48190a2d796677e4b3281 completed Feb. 28, 2026, 2:15 a.m.
NER Named-entity recognition batch_69a258808ff08190a06b6206f635612b completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a256425a488190959d71e39e699d90 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:20 a.m.