Triple

T7174670
Position Surface form Disambiguated ID Type / Status
Subject Joensuu E167288 entity
Predicate hasTwinTown P919 FINISHED
Object Petrozavodsk E101419 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: Petrozavodsk | Statement: [Joensuu, hasTwinTown, Petrozavodsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Petrozavodsk
Context triple: [Joensuu, hasTwinTown, Petrozavodsk]
  • A. Petrozavodsk, Russia chosen
    Petrozavodsk is the capital city of Russia’s Republic of Karelia, located on the western shore of Lake Onega and known as a regional cultural and industrial center.
  • B. Pskov
    Pskov is an ancient Russian city near the Estonian border, known for its medieval kremlin, historic churches, and role as a key fortress in northwestern Russia.
  • C. Muroran
    Muroran is an industrial port city in southern Hokkaido, Japan, known for its steel industry and scenic coastal landscapes.
  • D. Votkinsk
    Votkinsk is a Russian town in Udmurtia best known as the birthplace of composer Pyotr Ilyich Tchaikovsky.
  • E. Pskov, Russia
    Pskov, Russia is an ancient city in northwestern Russia near the Estonian border, known for its medieval kremlin, historic churches, and role as a key fortress in Russian history.
  • 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_69c68889a2748190a316c5e65360361a completed March 27, 2026, 1:39 p.m.
NER Named-entity recognition batch_69c6e88d770c8190b8d06dcd08447c08 completed March 27, 2026, 8:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7bf8a5d7c8190a7b52d46529dacb7 completed March 28, 2026, 11:46 a.m.
Created at: March 27, 2026, 2:48 p.m.