Triple

T16950019
Position Surface form Disambiguated ID Type / Status
Subject Vorokhta E411157 entity
Predicate locatedNear P294 FINISHED
Object Hoverla Mountain E86603 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: Hoverla Mountain | Statement: [Vorokhta, locatedNear, Hoverla Mountain]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hoverla Mountain
Context triple: [Vorokhta, locatedNear, Hoverla Mountain]
  • A. Hoverla chosen
    Hoverla is the tallest mountain in Ukraine, located in the Carpathian range and popular for hiking and tourism.
  • B. Goryashchaya Sopka
    Goryashchaya Sopka is an active stratovolcano located on Simushir Island in Russia’s Kuril Islands chain.
  • C. Mount Narodnaya
    Mount Narodnaya is a prominent peak in Russia known as the tallest mountain in the Ural range, marking the natural boundary between Europe and Asia.
  • D. Mount Karpinsky
    Mount Karpinsky is a prominent peak in the Ural Mountains of Russia, known as one of the higher summits in the range and a notable destination for mountaineers and hikers.
  • E. Chornohora
    Chornohora is a prominent mountain range in the Ukrainian Carpathians, known for containing some of the country’s highest peaks and scenic alpine landscapes.
  • 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_69d886c9c9d481909afe222093641cae completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cfb570b08190ae3385b0cad32668 completed April 18, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfeeee948190a5c8904d1f559a28 completed May 10, 2026, 6:35 p.m.
Created at: April 10, 2026, 5:31 a.m.