Triple

T7608996
Position Surface form Disambiguated ID Type / Status
Subject Mogilev Governorate E172183 entity
Predicate succeededBy P78 FINISHED
Object Gomel Governorate E308778 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: Gomel Governorate | Statement: [Mogilev Governorate, succeededBy, Gomel Governorate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gomel Governorate
Context triple: [Mogilev Governorate, succeededBy, Gomel Governorate]
  • A. Gomel Region chosen
    Gomel Region is an administrative region in southeastern Belarus known for its industrial centers, agricultural production, and proximity to the Chernobyl-affected areas.
  • B. Gomel District
    Gomel District is an administrative district in southeastern Belarus surrounding the city of Gomel.
  • C. Minsk Governorate
    Minsk Governorate was an administrative division of the Russian Empire and later the early Soviet state, centered on the city of Minsk in the historical region of Belarus.
  • 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_69c6994f50808190ba228764bb422417 completed March 27, 2026, 2:50 p.m.
NER Named-entity recognition batch_69c6fa1f6e888190ac6580724803fbc3 completed March 27, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c868600c7c81909cdeebdb5b2bdaf3 completed March 28, 2026, 11:46 p.m.
Created at: March 27, 2026, 3:54 p.m.