Triple

T15617887
Position Surface form Disambiguated ID Type / Status
Subject Verkhoyansky District E375464 entity
Predicate namedAfter P63 FINISHED
Object Verkhoyansk E75122 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: Verkhoyansk | Statement: [Verkhoyansky District, namedAfter, Verkhoyansk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verkhoyansk
Context triple: [Verkhoyansky District, namedAfter, Verkhoyansk]
  • A. Verkhoyansk chosen
    Verkhoyansk is a small town in the Sakha Republic of Russia known as one of the coldest permanently inhabited places on Earth.
  • B. Oymyakon
    Oymyakon is a remote rural locality in Russia’s Sakha Republic known as one of the coldest permanently inhabited places on Earth.
  • C. Ust-Kut
    Ust-Kut is a town in Irkutsk Oblast, Russia, located on the Lena River and known as a regional transport hub with river port and railway connections.
  • D. Mirny
    Mirny is a remote mining town in eastern Siberia best known for its massive open-pit diamond mine and role in Russia’s diamond industry.
  • E. Ust-Ilimsk
    Ust-Ilimsk is a Siberian city in Russia known for its large hydroelectric power station on the Angara River and its role in the region’s timber and energy industries.
  • 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e980b748190b43c0b650bf1e629 completed April 16, 2026, 2:51 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff678a9fac81908030726054ff5a99 completed May 9, 2026, 4:57 p.m.
Created at: April 10, 2026, 4:13 a.m.