Triple

T11112916
Position Surface form Disambiguated ID Type / Status
Subject Вішнева E262805 entity
Predicate hasNameInLanguage P15 FINISHED
Object Vishnevo E264471 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: Vishnevo | Statement: [Вішнева, hasNameInLanguage, Vishnevo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vishnevo
Context triple: [Вішнева, hasNameInLanguage, Vishnevo]
  • A. Vishnevo chosen
    Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
  • B. Volochysk
    Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
  • C. Dzerzhinovo
    Dzerzhinovo is a village in present-day Belarus best known as the birthplace of Soviet statesman and secret police founder Felix Dzerzhinsky.
  • D. Berdichev
    Berdichev is a historic city in present-day Ukraine, long known as a major center of Jewish life and commerce in Eastern Europe.
  • E. Novogrudok
    Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79aa523588190a25d241ccc6a9679 completed April 9, 2026, 12:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69e441cb16bc81908b5321506f655e38 completed April 19, 2026, 2:45 a.m.
Created at: April 8, 2026, 9:27 p.m.