Triple

T8292612
Position Surface form Disambiguated ID Type / Status
Subject Ukrainian Jews E193935 entity
Predicate notableHasidicDynastyOrigin P82576 FINISHED
Object Vizhnitz E140251 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: Vizhnitz | Statement: [Ukrainian Jews, notableHasidicDynastyOrigin, Vizhnitz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vizhnitz
Context triple: [Ukrainian Jews, notableHasidicDynastyOrigin, Vizhnitz]
  • A. Vizhnitz chosen
    Vizhnitz is a prominent Hasidic dynasty originating in Eastern Europe, known for its strong emphasis on communal life, joyous worship, and adherence to traditional Jewish scholarship and customs.
  • B. Tarnopol
    Tarnopol is a historic city in western Ukraine, now known as Ternopil, which has long served as a regional cultural and administrative center.
  • C. Radomyshl
    Radomyshl is a historic town in northern Ukraine, known for its Jewish heritage and role within the Zhytomyr Oblast region.
  • D. Vishnevo
    Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
  • E. Kraśnik
    Kraśnik is a town in eastern Poland known for its historical architecture and location within the Lublin region.
  • 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_69ca82e32db481908b72f3804fa71152 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cbd11ed22c819082bf036602eaa038 completed March 31, 2026, 1:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69cd6899b818819090c80a8eba7d5d4c completed April 1, 2026, 6:48 p.m.
Created at: March 30, 2026, 5:52 p.m.