Triple

T20682691
Position Surface form Disambiguated ID Type / Status
Subject Practical Kabbalah E508333 entity
Predicate oftenRestrictedTo P141031 FINISHED
Object highly learned practitioners 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: highly learned practitioners | Statement: [Practical Kabbalah, oftenRestrictedTo, highly learned practitioners]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenRestrictedTo
Context triple: [Practical Kabbalah, oftenRestrictedTo, highly learned practitioners]
  • A. eligibilityRestrictedBy
    Indicates that an entity’s eligibility for something is limited, constrained, or conditioned by another specified factor or rule.
  • B. mayHaveRestriction
    Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
  • C. productionRestrictedTo
    Indicates that the production or manufacture of something is limited or confined to a specified location, entity, or set of conditions.
  • D. notRestrictedBy
    Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
  • E. hadRestrictionsOn
    Indicates that one entity imposed or was subject to specific limitations, rules, or constraints regarding another entity or activity.
  • 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_69e0b4c1ed408190b72dd26b1e33f8a1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6bea9771881908a077d01f53f6d52 completed April 21, 2026, 12:02 a.m.
PD Predicate disambiguation batch_69e5c03caee881908be4dd25796a03d5 completed April 20, 2026, 5:57 a.m.
PDg Predicate description generation batch_69e5c3caef50819093c8159fe8d6435b completed April 20, 2026, 6:12 a.m.
Created at: April 16, 2026, 11:45 a.m.