Triple

T14095694
Position Surface form Disambiguated ID Type / Status
Subject Bein haMetzarim E339247 entity
Predicate musicRestriction P112802 FINISHED
Object customary avoidance of live music 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: customary avoidance of live music | Statement: [Bein haMetzarim, musicRestriction, customary avoidance of live music]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: musicRestriction
Context triple: [Bein haMetzarim, musicRestriction, customary avoidance of live music]
  • A. genreRestriction
    Indicates that there is a limitation or constraint on which genres are allowed or applicable in a given context.
  • B. musicUsed
    Indicates that one entity makes use of or incorporates another entity as music, such as in a performance, production, or media context.
  • C. licensingRestriction
    Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
  • D. politicalRestriction
    Indicates that there are limitations or prohibitions imposed on an entity’s political activities, rights, or participation.
  • E. regulatesMusic
    Indicates that one entity controls, governs, or sets rules for another entity’s music-related activities or outputs.
  • F. None of above. chosen

Provenance (4 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fb7fb3c819083266dbe7e93aaff completed April 14, 2026, 3:39 p.m.
PD Predicate disambiguation batch_69de05b2f7e481908a9a7d40153234c0 completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de2398856c81908bed6070e4ca6ab1 completed April 14, 2026, 11:23 a.m.
Created at: April 9, 2026, 10:22 p.m.