Triple

T3003949
Position Surface form Disambiguated ID Type / Status
Subject Novgorod Oblast E81852 entity
Predicate hasMajorCity P316 FINISHED
Object Borovichi E383200 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: Borovichi | Statement: [Novgorod Oblast, hasMajorCity, Borovichi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borovichi
Context triple: [Novgorod Oblast, hasMajorCity, Borovichi]
  • A. Borovichi chosen
    Borovichi is a town in western Russia known as an industrial and transport center situated on the Msta River.
  • B. Ostashkov
    Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
  • C. Skovorodino
    Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
  • D. Sosnovy Bor
    Sosnovy Bor is a Russian coastal town on the Gulf of Finland known for its large nuclear power plant and role as an energy and industrial center.
  • E. Pestovo
    Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
  • 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_69ad8b1c4de88190a83b7cefaa1f2842 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad9a149b248190ac4f11afc4871cc1 completed March 8, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4f00fe39481908cee24dc57be2b3b completed March 14, 2026, 5:20 a.m.
Created at: March 8, 2026, 2:59 p.m.