Triple

T14497575
Position Surface form Disambiguated ID Type / Status
Subject Sheksna River E359541 entity
Predicate hasSettlementOnBank P1010 FINISHED
Object Cherepovets E217616 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: Cherepovets | Statement: [Sheksna River, hasSettlementOnBank, Cherepovets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cherepovets
Context triple: [Sheksna River, hasSettlementOnBank, Cherepovets]
  • A. Cherepovets chosen
    Cherepovets is a major industrial city in northwestern Russia, known especially for its large steel production and chemical industries.
  • B. Votkinsk
    Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
  • C. 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.
  • D. 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.
  • E. Soligorsk
    Soligorsk is an industrial city in Belarus known for its large potash mining operations and location in the southern part of the Minsk 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_69d8279740308190af9df93a3af8592e completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de9311cc748190880c784f173b7f2b completed April 14, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0025e6bc748190b8099e7559569a90 completed May 10, 2026, 6:29 a.m.
Created at: April 10, 2026, 1:21 a.m.