Triple

T9730569
Position Surface form Disambiguated ID Type / Status
Subject Siberian Khanate E235727 entity
Predicate capital P234 FINISHED
Object Isker
Isker was the historic capital city of the Siberian Khanate, serving as its main political and administrative center in western Siberia.
 E817998 NE FINISHED

How this triple was built (4 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: Isker | Statement: [Siberian Khanate, capital, Isker]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Isker
Context triple: [Siberian Khanate, capital, Isker]
  • A. Ozerki
    Ozerki is a locality in Russia historically noted as the site where the revolutionary priest Georgy Gapon was killed.
  • B. Rissne
    Rissne is a residential district and urban area in the Stockholm metropolitan region of Sweden, known for its mix of apartment housing and proximity to public transit.
  • C. Nagatinskaya
    Nagatinskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the Nagatinsky Zaton area of southern Moscow.
  • D. Bory
    Bory is a Hungarian surname most notably associated with Jenő Bory, a sculptor, architect, and creator of the famous Bory Castle in Székesfehérvár, Hungary.
  • E. Dzvina
    Dzvina is the Belarusian name for the Daugava River, a major Eastern European river flowing through Russia, Belarus, and Latvia into the Baltic Sea.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Isker
Triple: [Siberian Khanate, capital, Isker]
Generated description
Isker was the historic capital city of the Siberian Khanate, serving as its main political and administrative center in western Siberia.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Isker
Target entity description: Isker was the historic capital city of the Siberian Khanate, serving as its main political and administrative center in western Siberia.
  • A. Ozerki
    Ozerki is a locality in Russia historically noted as the site where the revolutionary priest Georgy Gapon was killed.
  • B. Rissne
    Rissne is a residential district and urban area in the Stockholm metropolitan region of Sweden, known for its mix of apartment housing and proximity to public transit.
  • C. Nagatinskaya
    Nagatinskaya is a Moscow Metro station serving the Serpukhovsko–Timiryazevskaya Line in the Nagatinsky Zaton area of southern Moscow.
  • D. Bory
    Bory is a Hungarian surname most notably associated with Jenő Bory, a sculptor, architect, and creator of the famous Bory Castle in Székesfehérvár, Hungary.
  • E. Dzvina
    Dzvina is the Belarusian name for the Daugava River, a major Eastern European river flowing through Russia, Belarus, and Latvia into the Baltic Sea.
  • F. None of above. chosen

Provenance (5 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_69ca84d0fad481909cdd45aa77416c48 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9eb2373c81909139c7a2ff2aa541 completed April 1, 2026, 10:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1afba5ec081908044a4aefdc6f9ee completed April 5, 2026, 12:41 a.m.
NEDg Description generation batch_69d1b0dde93881908fcec28de9cfa99d completed April 5, 2026, 12:46 a.m.
NED2 Entity disambiguation (via description) batch_69d1b1bbe6108190af17b75f79c0f465 completed April 5, 2026, 12:50 a.m.
Created at: March 30, 2026, 8:21 p.m.