Triple

T18182761
Position Surface form Disambiguated ID Type / Status
Subject Vitebsk Region E435331 entity
Predicate borderWith P224 FINISHED
Object Mogilev Region 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: Mogilev Region | Statement: [Vitebsk Region, borderWith, Mogilev Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mogilev Region
Context triple: [Vitebsk Region, borderWith, Mogilev Region]
  • A. Mogilev Region chosen
    Mogilev Region is an administrative region in eastern Belarus known for its industrial centers, agricultural production, and location along the Dnieper River.
  • B. Minsk Region
    Minsk Region is an administrative region in central Belarus that surrounds, but does not include, the national capital city of Minsk.
  • C. Vitebsk Region
    Vitebsk Region is an administrative region in northeastern Belarus known for its historical cities, cultural heritage, and diverse natural landscapes.
  • D. Mogilev Governorate
    Mogilev Governorate was an administrative division of the Russian Empire located in the historical region of eastern Belarus.
  • E. Grodno Region
    Grodno Region is an administrative region in western Belarus known for its historic cities, diverse cultural heritage, and location along the borders with Poland and Lithuania.
  • 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_69d8b90c7ec081909b4694ccecb449c6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dffc432c8190af53da5256dc476c completed April 19, 2026, 2 p.m.
Created at: April 10, 2026, 10:31 a.m.