Triple

T18182748
Position Surface form Disambiguated ID Type / Status
Subject Vitebsk Region E435331 entity
Predicate hasCity P316 FINISHED
Object Orsha 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: Orsha | Statement: [Vitebsk Region, hasCity, Orsha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Orsha
Context triple: [Vitebsk Region, hasCity, Orsha]
  • A. Orsha chosen
    Orsha is a historic city in eastern Belarus known as a regional transport hub and site of several significant battles.
  • B. Moghiliov-Podolsk
    Moghiliov-Podolsk is the Romanian name for Mogilev-Podilskyi, a city in western Ukraine located on the Dniester River near the border with Moldova.
  • C. Borisoglebsk
    Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
  • D. Kozelsk
    Kozelsk is a historic town in western Russia known for its medieval defenses and location within Kaluga Oblast.
  • E. Vitebsk
    Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
  • 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.