Triple

T8809042
Position Surface form Disambiguated ID Type / Status
Subject Brest Region E209608 entity
Predicate bordersWith P224 FINISHED
Object Gomel Region 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 Region | Statement: [Brest Region, bordersWith, Gomel Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gomel Region
Context triple: [Brest Region, bordersWith, Gomel Region]
  • 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. Mogilev Region
    Mogilev Region is an administrative region in eastern Belarus known for its industrial centers, agricultural production, and location along the Dnieper River.
  • 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. Vitebsk Region
    Vitebsk Region is an administrative region in northeastern Belarus known for its historical cities, cultural heritage, and diverse natural landscapes.
  • 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_69ca8363f3308190a47e3f1ebd51f613 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5fd4cbec8190a929d4e60da8ad65 completed March 31, 2026, 11:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0772ba2808190b8b7948a09b8dee5 completed April 4, 2026, 2:27 a.m.
Created at: March 30, 2026, 6:45 p.m.