Triple

T22640416
Position Surface form Disambiguated ID Type / Status
Subject Yisrael Lipkin E558808 entity
Predicate residence P75 FINISHED
Object Kovno 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: Kovno | Statement: [Yisrael Lipkin, residence, Kovno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kovno
Context triple: [Yisrael Lipkin, residence, Kovno]
  • A. Kovno chosen
    Kovno is the historical name for Kaunas, a major city in Lithuania that was once part of the Russian Empire and had a significant Jewish community.
  • B. Mitau
    Mitau, historically known as the capital of the Duchy of Courland and Semigallia, is the former German name for the city now called Jelgava in present-day Latvia.
  • C. Alytus
    Alytus is a city in southern Lithuania known as a regional cultural and economic center on the banks of the Nemunas River.
  • D. Vilna
    Vilna is the historical name for Vilnius, the capital city of Lithuania and a major cultural and political center of the region.
  • E. Vilkaviškis
    Vilkaviškis is a town in southwestern Lithuania known as an administrative and historical center of the surrounding agricultural region.
  • 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_69e24547f7fc819086e2c4ba3b979657 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f170116fe881908178cffef26e3ae7 completed April 29, 2026, 2:42 a.m.
Created at: April 17, 2026, 3:04 p.m.