Triple

T4631562
Position Surface form Disambiguated ID Type / Status
Subject Arkhangelsk E101428 entity
Predicate hasAlternativeName P39 FINISHED
Object Archangelsk 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: Archangelsk | Statement: [Arkhangelsk, hasAlternativeName, Archangelsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Archangelsk
Context triple: [Arkhangelsk, hasAlternativeName, Archangelsk]
  • 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. Tomsk
    Tomsk is a historic university and research city in southwestern Siberia, known as one of the region’s oldest and most important cultural and educational centers.
  • E. Novo-Arkhangelsk
    Novo-Arkhangelsk was the Russian colonial-era name for the settlement that later became the city of Sitka in present-day Alaska.
  • 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_69bd43d2f1c081908cd4b7ec48ecc73d completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a32d6408190962e60b9bce7560d completed March 20, 2026, 2:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69be10330b608190a82e67ceac3b34b7 completed March 21, 2026, 3:27 a.m.
Created at: March 20, 2026, 1:13 p.m.