Triple

T2831963
Position Surface form Disambiguated ID Type / Status
Subject YAKST E62257 entity
Predicate usedInCity P4810 FINISHED
Object Yakutsk E23786 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: Yakutsk | Statement: [YAKST, usedInCity, Yakutsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yakutsk
Context triple: [YAKST, usedInCity, Yakutsk]
  • A. Yakutsk chosen
    Yakutsk is a major city in northeastern Siberia, Russia, known as one of the coldest large cities in the world and a key administrative and cultural center of the Sakha Republic.
  • B. Irkutsk
    Irkutsk is a major city in southeastern Siberia, Russia, historically significant as a political and administrative center and a key hub during the Russian Civil War.
  • C. Magadan
    Magadan is a remote port city in Russia’s Far East, known historically as a gateway to the Kolyma region and its former Gulag labor camps.
  • D. Tyumen
    Tyumen is a historic city in western Siberia, Russia, known as an early Russian settlement in Siberia and now a major industrial and administrative center.
  • E. Salekhard
    Salekhard is a Russian Arctic city located on the Ob River and notable as the only city in the world situated directly on the Arctic Circle.
  • 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_69ab4c3c39188190955b9c49d98463d8 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdebe95188190bf65fb4cd88e2ec5 completed March 7, 2026, 8:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69b20f2e10b0819090455b876abe821b completed March 12, 2026, 12:56 a.m.
Created at: March 6, 2026, 10:01 p.m.