Triple

T15542231
Position Surface form Disambiguated ID Type / Status
Subject Khanty-Mansi Autonomous Okrug E370506 entity
Predicate hasMajorCity P316 FINISHED
Object Khanty-Mansiysk E330998 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: Khanty-Mansiysk | Statement: [Khanty-Mansi Autonomous Okrug, hasMajorCity, Khanty-Mansiysk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khanty-Mansiysk
Context triple: [Khanty-Mansi Autonomous Okrug, hasMajorCity, Khanty-Mansiysk]
  • A. Khanty-Mansiysk chosen
    Khanty-Mansiysk is a city in western Siberia, Russia, known as the administrative center of the oil-rich Khanty-Mansi Autonomous Okrug.
  • B. Pelym Mansi
    Pelym Mansi is a regional dialect group of the Northern Mansi language traditionally spoken around the Pelym River area in western Siberia.
  • C. Nizhnevartovsk
    Nizhnevartovsk is a major oil-producing city in western Siberia, Russia, known as one of the centers of the country’s petroleum industry.
  • D. Ostyak
    Ostyak is an alternative name for the Khanty language, a Uralic language spoken by the Khanty people of western Siberia in Russia.
  • E. 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.
  • 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_69d85cc521a08190921fb50319dddc34 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04432c3808190bb5b653bf8de30c6 completed April 16, 2026, 2:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffdbba9fb08190b800af317f0c9abf completed May 10, 2026, 1:13 a.m.
Created at: April 10, 2026, 4:07 a.m.