Triple

T17097819
Position Surface form Disambiguated ID Type / Status
Subject Belorussian strategic offensive operation E414893 entity
Predicate capturedCity P8411 FINISHED
Object Minsk E43503 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: Minsk | Statement: [Belorussian strategic offensive operation, capturedCity, Minsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Minsk
Context triple: [Belorussian strategic offensive operation, capturedCity, Minsk]
  • A. Minsk chosen
    Minsk is the capital and largest city of Belarus, serving as its political, economic, and cultural center.
  • B. Gomel
    Gomel is a major city in southeastern Belarus, serving as an important cultural, industrial, and economic center near the border with Russia and Ukraine.
  • C. Brest (Belarus)
    Brest is a city in southwestern Belarus near the Polish border, known as a major transport hub and for the historic Brest Fortress, a key World War II memorial.
  • D. Mogilev
    Mogilev is a major city in eastern Belarus known as an important industrial and cultural center on the Dnieper River.
  • E. Vilna
    Vilna is the historical name for Vilnius, the capital city of Lithuania and a major cultural and political center of the 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbffafb08190baf9e0b4fdf1b404 completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012eefd5f08190b9eb8a81e45a9921 completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:35 a.m.