Triple

T4488241
Position Surface form Disambiguated ID Type / Status
Subject Binghamton, New York E107301 entity
Predicate hasSisterCity P919 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: [Binghamton, New York, hasSisterCity, Borovichi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borovichi
Context triple: [Binghamton, New York, hasSisterCity, Borovichi]
  • A. Borovichi chosen
    Borovichi is a town in western Russia known as an industrial and transport center situated on the Msta River.
  • B. Feodorovsky Gorodok
    Feodorovsky Gorodok is a historic architectural complex in Pushkin, Russia, built in a neo-Russian style as a residence and military settlement associated with the last Russian imperial family.
  • C. Ostashkov
    Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
  • D. Skovorodino
    Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
  • E. 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.
  • 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_69bd43f84f788190a1383579c4a595be completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd52ad36748190b791de458f2116b2 completed March 20, 2026, 1:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69be5c70e6cc8190b447d3bd1f578aae completed March 21, 2026, 8:53 a.m.
Created at: March 20, 2026, 12:59 p.m.