Triple

T21954805
Position Surface form Disambiguated ID Type / Status
Subject Sefer HaLikkutim E542158 entity
Predicate subject P450 FINISHED
Object cosmic repair (tikkun) NE NERFINISHED

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: cosmic repair (tikkun) | Statement: [Sefer HaLikkutim, subject, cosmic repair (tikkun)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: cosmic repair (tikkun)
Context triple: [Sefer HaLikkutim, subject, cosmic repair (tikkun)]
  • A. Tikkun HaNefesh
    Tikkun HaNefesh is a Jewish spiritual concept and practice focused on healing, refining, and elevating the individual soul through ethical behavior, prayer, and inner work.
  • B. cosmic Christ
    The cosmic Christ is a theological concept portraying Christ as the universal, all-encompassing presence of God active in the entire cosmos and throughout evolutionary creation.
  • C. Tikun chosen
    Tikun is a central Kabbalistic concept referring to the spiritual rectification and restoration of cosmic and personal harmony.
  • D. Tikkun Olam
    Tikkun Olam is a Jewish theological and ethical concept emphasizing human responsibility to repair, improve, and perfect the world through justice, compassion, and righteous action.
  • E. Cosmonic
    Cosmonic is a cloud-native platform company focused on building and running distributed applications using WebAssembly and the wasmCloud framework.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c47ef0e48190a50e1bcc43f4b3fd completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1243f46dc819097e4a1849af7fba4 completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 7:59 p.m.