Triple

T7481568
Position Surface form Disambiguated ID Type / Status
Subject Koszalin E176769 entity
Predicate twinTown 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: [Koszalin, twinTown, Brest]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brest
Context triple: [Koszalin, twinTown, 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. Pinsk
    Pinsk is a historic city in southwestern Belarus, known for its location on the Pina River and its rich cultural and architectural heritage.
  • D. Lvov
    Lvov is a Russian noble family name most notably borne by Georgy Lvov, the first head of the Russian Provisional Government after the February Revolution of 1917.
  • E. Żory
    Żory is a city in southern Poland known for its historical roots in the Silesian region and its mix of industrial and residential character.
  • 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_69c69f236ce08190a04d7679f03b29b2 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f534aa388190b3bb3e16be3a54c8 completed March 27, 2026, 9:23 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83493f0988190b8c569d34bbe2817 completed March 28, 2026, 8:05 p.m.
Created at: March 27, 2026, 3:42 p.m.