Triple

T1957723
Position Surface form Disambiguated ID Type / Status
Subject Archangel E42307 entity
Predicate hasAlternativeName P39 FINISHED
Object Archangel’sk E101428 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: Archangel’sk | Statement: [Archangel, hasAlternativeName, Archangel’sk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Archangel’sk
Context triple: [Archangel, hasAlternativeName, Archangel’sk]
  • A. Arkhangelsk chosen
    Arkhangelsk is a historic port city in northern Russia on the White Sea, long serving as a key maritime gateway and administrative center of the surrounding region.
  • B. Murmansk
    Murmansk is a major Arctic port city in northwestern Russia, known for its ice-free harbor and strategic military and shipping importance.
  • 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. Novo-Arkhangelsk
    Novo-Arkhangelsk was the Russian colonial-era name for the settlement that later became the city of Sitka in present-day Alaska.
  • E. Severomorsk
    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.
  • 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_69a8870eea088190a38781990812a9bc completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb37c60148190823f6a2a73b949e8 completed March 7, 2026, 5:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae71a548408190b8c8c97c94336e2d completed March 9, 2026, 7:07 a.m.
Created at: March 4, 2026, 7:36 p.m.