Triple

T10108373
Position Surface form Disambiguated ID Type / Status
Subject Kolyma Tales E218179 entity
Predicate setting P1957 FINISHED
Object Kolyma E497605 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: Kolyma | Statement: [Kolyma Tales, setting, Kolyma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kolyma
Context triple: [Kolyma Tales, setting, Kolyma]
  • A. Kolyma River basin
    The Kolyma River basin is a vast, sparsely populated watershed in northeastern Siberia that drains into the Arctic Ocean and is known for its extreme cold, permafrost landscapes, and historical association with Soviet-era labor camps.
  • B. Kolyma River chosen
    The Kolyma River is a major waterway in northeastern Siberia, Russia, known for its harsh Arctic environment and historical association with Soviet-era labor camps.
  • C. Yakut
    Yakut is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
  • D. Ozyornaya
    Ozyornaya is a Moscow Metro station on the Kalininsko–Solntsevskaya Line serving the western part of the city.
  • E. Anadyr
    Anadyr is a remote Arctic port town in Russia’s Far East, situated on the Anadyr River near the Bering Sea and serving as the main administrative, economic, and cultural center of the surrounding region.
  • 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_69ca83da93fc8190b54e44bc2b34857c completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cdd0cbd8a48190b2af6177d1249f58 completed April 2, 2026, 2:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2e59ec83c8190a79fbb0d0de90310 completed April 5, 2026, 10:43 p.m.
Created at: March 30, 2026, 9:03 p.m.