Triple

T4064037
Position Surface form Disambiguated ID Type / Status
Subject Western Belarus E86281 entity
Predicate majorCity P316 FINISHED
Object Pinsk E153073 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: Pinsk | Statement: [Western Belarus, majorCity, Pinsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pinsk
Context triple: [Western Belarus, majorCity, Pinsk]
  • A. Pinsk chosen
    Pinsk is a historic city in southwestern Belarus, known for its location on the Pina River and its rich cultural and architectural heritage.
  • B. Novopolotsk
    Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
  • C. Vitebsk
    Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
  • D. 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.
  • 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_69aed93c69208190a4efac0efe3cd69b completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefbd7896c81909c61ed0d910d9c5f completed March 9, 2026, 4:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f18218881908c95266c6b18ad47 completed March 14, 2026, 3:30 p.m.
Created at: March 9, 2026, 3:38 p.m.