Triple

T5778101
Position Surface form Disambiguated ID Type / Status
Subject Belukha Mountain E127493 entity
Predicate isAlsoKnownAs P39 FINISHED
Object Belukha E127493 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: Belukha | Statement: [Belukha Mountain, isAlsoKnownAs, Belukha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belukha
Context triple: [Belukha Mountain, isAlsoKnownAs, Belukha]
  • A. Belukha Mountain chosen
    Belukha Mountain is a prominent, glaciated peak in the Altai range of Siberia, renowned for its dramatic alpine scenery and significance in Russian mountaineering.
  • B. Bezymianny
    Bezymianny is an active stratovolcano on Russia’s Kamchatka Peninsula, known for its catastrophic 1956 eruption and ongoing explosive activity.
  • C. Pevek
    Pevek is a small Arctic port town in Russia, known as one of the northernmost settlements in the country and a key hub in the Chukotka region.
  • D. East Belukha
    East Belukha is one of the twin summits of Belukha Mountain in the Altai range, known for its glaciated slopes and challenging alpine climbing routes.
  • E. Pechenga
    Pechenga is a region in Russia’s far northwest, near the Barents Sea and the Norwegian border, historically known as Petsamo when it belonged to Finland.
  • 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_69c008361fa88190aefa4dc41b051e7f completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029e107348190a03086f1cbfae0d3 completed March 22, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b0d1ddb48190a697f202b43cc633 completed March 23, 2026, 3:17 a.m.
Created at: March 22, 2026, 3:50 p.m.