Triple

T20407242
Position Surface form Disambiguated ID Type / Status
Subject Celje E500500 entity
Predicate hasTwinTown P919 FINISHED
Object Cherepovets NE NERFINISHED

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: Cherepovets | Statement: [Celje, hasTwinTown, Cherepovets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cherepovets
Context triple: [Celje, hasTwinTown, Cherepovets]
  • A. Cherepovets chosen
    Cherepovets is a major industrial city in northwestern Russia, known especially for its large steel production and chemical industries.
  • B. Koporye
    Koporye is a historic village in Leningrad Oblast, Russia, best known for its medieval fortress and strategic location near the Gulf of Finland.
  • C. Votkinsk
    Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
  • D. Volokolamsk
    Volokolamsk is a historic town in western Russia, located northwest of Moscow and known for its medieval origins and role in regional trade and defense.
  • E. Solikamsk
    Solikamsk is a historic industrial city in Russia known for its major salt and chemical industries and its location in the northern part of Perm Krai.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4a81bec8190b69adfdc1336a015 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67993dc7081908ebd54ec92e712ea completed April 20, 2026, 7:08 p.m.
Created at: April 16, 2026, 11:29 a.m.