Triple

T4992678
Position Surface form Disambiguated ID Type / Status
Subject Avgad E112168 entity
Predicate associatedWith P37 FINISHED
Object Temurah E263692 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: Temurah | Statement: [Avgad, associatedWith, Temurah]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Temurah
Context triple: [Avgad, associatedWith, Temurah]
  • A. Temurah
    Temurah is a Kabbalistic method of letter substitution and permutation used to uncover hidden meanings within Hebrew scripture.
  • B. Temurah chosen
    Temurah is a Talmudic tractate in the Order of Kodashim that discusses the laws of substituting one sacrificial animal for another and related sanctity issues.
  • C. Shevirat ha-Kelim
    Shevirat ha-Kelim is a central Lurianic Kabbalistic doctrine describing the primordial “shattering of the vessels,” a cosmic catastrophe that scatters divine sparks throughout creation and underlies the need for spiritual repair (tikkun).
  • D. Taslḥit
    Taslḥit is a variety of the Amazigh (Berber) language spoken primarily in southwestern Morocco.
  • E. Kodashim
    Kodashim is the order of the Mishnah that deals with sacrificial rites, Temple service, and other holy offerings and sancta in Jewish law.
  • 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_69bd441be7bc8190b530362d427b97d2 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd729bb45081908d85891a9d9f4b71 completed March 20, 2026, 4:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a2d71c08190be1d3397585ca65c completed March 21, 2026, 12:08 p.m.
Created at: March 20, 2026, 1:34 p.m.