Triple

T8871290
Position Surface form Disambiguated ID Type / Status
Subject Cherkessk E211161 entity
Predicate formerName P65 FINISHED
Object Yezhovo-Cherkessk E211161 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: Yezhovo-Cherkessk | Statement: [Cherkessk, formerName, Yezhovo-Cherkessk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yezhovo-Cherkessk
Context triple: [Cherkessk, formerName, Yezhovo-Cherkessk]
  • A. Cherkessk chosen
    Cherkessk is a city in southwestern Russia that serves as the administrative, economic, and cultural center of the Karachay-Cherkess Republic in the North Caucasus.
  • B. Yuzovka
    Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
  • C. Yegoryevsk
    Yegoryevsk is a historic town in Russia, now part of Moscow Oblast, known for its 19th-century architecture and industrial heritage.
  • D. Syzran
    Syzran is a historic industrial city on the Volga River in western Russia, known for its oil refining, engineering industries, and regional transport significance.
  • E. Kamyshin
    Kamyshin is a significant industrial and river port city on the Volga River in southwestern Russia.
  • 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_69ca838d3c7c8190a849566d5afd2b11 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6126d2f88190979ab25772ee657c completed April 1, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfa0ea9f5c8190b5c32fb1fefdc68b completed April 3, 2026, 11:13 a.m.
Created at: March 30, 2026, 6:51 p.m.