Triple

T15216006
Position Surface form Disambiguated ID Type / Status
Subject Kola Bay E363637 entity
Predicate hasCityOnShore P969 FINISHED
Object Severomorsk E222361 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: Severomorsk | Statement: [Kola Bay, hasCityOnShore, Severomorsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Severomorsk
Context triple: [Kola Bay, hasCityOnShore, Severomorsk]
  • A. Severomorsk chosen
    Severomorsk is a closed naval town in Russia’s Murmansk Oblast that serves as the main base of the Russian (formerly Soviet) Northern Fleet on the Barents Sea.
  • B. Sestroretsk
    Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
  • C. Severodvinsk
    Severodvinsk is a Russian port city on the White Sea, known as a major center for the construction and maintenance of nuclear submarines.
  • D. Tuapse
    Tuapse is a Black Sea port town in southern Russia known as a seaside resort and industrial center within Krasnodar Krai.
  • E. Krasnoufimsk
    Krasnoufimsk is a small historic town in Russia’s Ural region, known for its traditional architecture and role as a local administrative and cultural 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0076e4348819091fa91c1562e7c5c completed April 15, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef687bdc819090ec8a4e1af9f422 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:11 a.m.