Triple

T1311952
Position Surface form Disambiguated ID Type / Status
Subject Białystok E28010 entity
Predicate twinCity P1072 FINISHED
Object Brest E41676 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: Brest | Statement: [Białystok, twinCity, Brest]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brest
Context triple: [Białystok, twinCity, Brest]
  • A. Brest
    Brest is a major port city in northwestern France that serves as one of the country’s principal naval and maritime centers.
  • B. Brest (Belarus) chosen
    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.
  • C. Białystok
    Białystok is a city in northeastern Poland best known as the birthplace of L. L. Zamenhof and the cradle of the international language Esperanto.
  • D. Wilno
    Wilno is the historical Polish name for Vilnius, a major cultural and political center of the region that served as an important city in the interwar Second Polish Republic.
  • E. Hrodna
    Hrodna is a historic city in western Belarus known for its well-preserved architecture and role as a major cultural and economic 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_69a498532c3481909223b74af2e578df completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c1572b1c8190ab978198c2d655c8 completed March 1, 2026, 10:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69acbaeeece08190a805a2f037e709ce completed March 7, 2026, 11:55 p.m.
Created at: March 1, 2026, 7:55 p.m.