Triple

T12908111
Position Surface form Disambiguated ID Type / Status
Subject Gomel Region E308778 entity
Predicate hasIndustrialCenter P3436 FINISHED
Object Zhlobin E1019586 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: Zhlobin | Statement: [Gomel Region, hasIndustrialCenter, Zhlobin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zhlobin
Context triple: [Gomel Region, hasIndustrialCenter, Zhlobin]
  • A. Zhlobin chosen
    Zhlobin is an industrial city in southeastern Belarus, known especially for its major steel production facilities and location on the Dnieper River.
  • B. Volkovysk
    Volkovysk is a historic town in present-day Belarus, known for its centuries-old Jewish community and changing rule under various Eastern European states.
  • C. Novogrudok
    Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
  • D. Novopolotsk
    Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
  • E. Horodnia
    Horodnia is a small town in northern Ukraine known for its historical roots and location within the Chernihiv 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_69d7bdf92b588190acdf2a2291ac4590 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9719d4d1c8190a2c4f362e1772a73 completed April 10, 2026, 9:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6eacc2f808190bcc6817b7ce82750 completed May 3, 2026, 6:27 a.m.
Created at: April 9, 2026, 5:41 p.m.