Triple

T8608095
Position Surface form Disambiguated ID Type / Status
Subject Viskuli E203852 entity
Predicate region P40 FINISHED
Object Western Belarus E86281 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: Western Belarus | Statement: [Viskuli, region, Western Belarus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Western Belarus
Context triple: [Viskuli, region, Western Belarus]
  • A. Western Belarus chosen
    Western Belarus is the historical region of Belarus that was incorporated into the Second Polish Republic after World War I and later annexed by the Soviet Union during World War II.
  • B. Belarus region
    The Belarus region is a historical area in Eastern Europe that served as a crucial battleground during Napoleon’s 1812 invasion of the Russian Empire.
  • C. 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.
  • D. Minsk Region
    Minsk Region is an administrative region in central Belarus that surrounds, but does not include, the national capital city of Minsk.
  • E. Mogilev Region
    Mogilev Region is an administrative region in eastern Belarus known for its industrial centers, agricultural production, and location along the Dnieper River.
  • 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_69ca832c23e4819095a9f3eea4a21828 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cc46ec301881908ce148a3f07069fe completed March 31, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69cea909757c819095dd38644c21af33 completed April 2, 2026, 5:36 p.m.
Created at: March 30, 2026, 6:25 p.m.