Triple

T11423965
Position Surface form Disambiguated ID Type / Status
Subject Vishneva E270696 entity
Predicate hasAlternativeName P39 FINISHED
Object Vishneve E481918 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: Vishneve | Statement: [Vishneva, hasAlternativeName, Vishneve]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vishneve
Context triple: [Vishneva, hasAlternativeName, Vishneve]
  • A. Vishnevo
    Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
  • B. Dzerzhinovo
    Dzerzhinovo is a village in present-day Belarus best known as the birthplace of Soviet statesman and secret police founder Felix Dzerzhinsky.
  • C. Vizhnitz
    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.
  • D. Volochysk
    Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
  • E. Vyshneve chosen
    Vyshneve is a small suburban city near Kyiv in northern Ukraine, known primarily as a residential and commuter town within the Kyiv metropolitan area.
  • 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_69d6aadeef688190874bcecd88b3dd9b completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d806be9c2c819084da13101cbb6c81 completed April 9, 2026, 8:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5d36004cc81908222321af88d2903 completed April 20, 2026, 7:18 a.m.
Created at: April 8, 2026, 9:35 p.m.