Triple

T12640642
Position Surface form Disambiguated ID Type / Status
Subject Grodno Region E301887 entity
Predicate hasHistoricCity P3786 FINISHED
Object Volkovysk E359922 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: Volkovysk | Statement: [Grodno Region, hasHistoricCity, Volkovysk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Volkovysk
Context triple: [Grodno Region, hasHistoricCity, Volkovysk]
  • A. Volkovysk chosen
    Volkovysk is a historic town in present-day Belarus, known for its centuries-old Jewish community and changing rule under various Eastern European states.
  • B. Novopolotsk
    Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
  • C. Novogrudok
    Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
  • D. Vitebsk
    Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
  • E. Horodnia
    Horodnia is a small town in northern Ukraine known for its historical roots and location within the Chernihiv 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_69d7bdec9f9c8190b4bac675b7588211 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9614ae6ac8190b42acbf2b0331fda completed April 10, 2026, 8:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6c0d89b988190bde04701c4d1f904 completed May 3, 2026, 3:28 a.m.
Created at: April 9, 2026, 5:17 p.m.