Triple

T19388600
Position Surface form Disambiguated ID Type / Status
Subject Kurgan Oblast E484998 entity
Predicate namedAfter P63 FINISHED
Object city of Kurgan NE NERFINISHED

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: city of Kurgan | Statement: [Kurgan Oblast, namedAfter, city of Kurgan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Kurgan
Context triple: [Kurgan Oblast, namedAfter, city of Kurgan]
  • A. Kurgan chosen
    Kurgan is a city in southwestern Siberia, Russia, known as an administrative, industrial, and transport center near the Ural Mountains.
  • B. Korgas City
    Korgas City is a county-level city in China’s Xinjiang region, known as a key border crossing and trade hub between China and Kazakhstan.
  • C. Puzrish-Dagan
    Puzrish-Dagan was a major Ur III-period Mesopotamian administrative center known for its extensive archive of economic and bureaucratic cuneiform tablets.
  • D. Kurn
    Kurn is a Klingon warrior and the younger brother of Worf in the Star Trek universe.
  • E. Uch-Kurgan
    Uch-Kurgan is a town in Kyrgyzstan known for its location on the Naryn River and its role in regional hydropower and agriculture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61b425e848190ab5ae8ae0a034fe2 completed April 20, 2026, 12:25 p.m.
Created at: April 10, 2026, 1:36 p.m.