Triple

T23193944
Position Surface form Disambiguated ID Type / Status
Subject Menachem Mendel of Vitebsk E579822 entity
Predicate associatedWithCity P1481 FINISHED
Object Horodok 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: Horodok | Statement: [Menachem Mendel of Vitebsk, associatedWithCity, Horodok]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Horodok
Context triple: [Menachem Mendel of Vitebsk, associatedWithCity, Horodok]
  • A. Horodok chosen
    Horodok is a small town in western Ukraine known for its historical roots and location within the Khmelnytskyi region.
  • B. Matorf
    Matorf is a district or locality within the town of Lemgo in the German state of North Rhine-Westphalia.
  • C. Horodnia
    Horodnia is a small town in northern Ukraine known for its historical roots and location within the Chernihiv region.
  • D. Radomyshl
    Radomyshl is a historic town in northern Ukraine, known for its Jewish heritage and role within the Zhytomyr Oblast region.
  • E. Tarnopol
    Tarnopol is a historic city in western Ukraine, now known as Ternopil, which has long served as a regional cultural and administrative center.
  • 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_69e24600eed08190bd7e5295653a1503 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18fd971d08190a132d24094e0c37b completed April 29, 2026, 4:58 a.m.
Created at: April 17, 2026, 4:06 p.m.