Triple

T21453929
Position Surface form Disambiguated ID Type / Status
Subject Sefer Noam Elimelech E529288 entity
Predicate associatedPlace P1481 FINISHED
Object Lizhensk 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: Lizhensk | Statement: [Sefer Noam Elimelech, associatedPlace, Lizhensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lizhensk
Context triple: [Sefer Noam Elimelech, associatedPlace, Lizhensk]
  • A. Lizhensk chosen
    Lizhensk is a historic town in southeastern Poland best known as a major center of early Hasidic Judaism and the home and burial place of Rabbi Elimelech of Lizhensk.
  • B. Volodarsk
    Volodarsk is a town in Nizhny Novgorod Oblast, Russia, known for its location along the Klyazma River and its industrial character.
  • C. Melnikovo
    Melnikovo is a rural settlement located within the Priozersky District of Leningrad Oblast in northwestern Russia.
  • D. Pestovo
    Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
  • E. Andrusovo
    Andrusovo is a historic village in present-day Belarus known as the site where the 1667 Truce of Andrusovo between the Polish–Lithuanian Commonwealth and Tsardom of Russia was concluded.
  • 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_69e0c457579481909db68053ed99750c completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9e9d50b88819081a771596d0a2b2b completed April 23, 2026, 9:43 a.m.
Created at: April 16, 2026, 6:07 p.m.