Triple

T14170407
Position Surface form Disambiguated ID Type / Status
Subject Villiers-le-Bel E351189 entity
Predicate hasTwinTown P919 FINISHED
Object Mogilev E220170 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: Mogilev | Statement: [Villiers-le-Bel, hasTwinTown, Mogilev]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mogilev
Context triple: [Villiers-le-Bel, hasTwinTown, Mogilev]
  • A. Mogilev chosen
    Mogilev is a major city in eastern Belarus known as an important industrial and cultural center on the Dnieper River.
  • B. Gomel
    Gomel is a major city in southeastern Belarus, serving as an important cultural, industrial, and economic center near the border with Russia and Ukraine.
  • C. Novopolotsk
    Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
  • D. Vitebsk
    Vitebsk is a historic city in northeastern Belarus known as a major cultural center and the birthplace of artist Marc Chagall.
  • E. Moghiliov-Podolsk
    Moghiliov-Podolsk is the Romanian name for Mogilev-Podilskyi, a city in western Ukraine located on the Dniester River near the border with Moldova.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61b472288190b4a271daa54aa6cd completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf7f779248190921c85f99f587296 completed May 7, 2026, 8:37 p.m.
Created at: April 10, 2026, 1:01 a.m.