Triple

T21381879
Position Surface form Disambiguated ID Type / Status
Subject Novokuznetsk E527378 entity
Predicate formerName P65 FINISHED
Object Kuznetsk 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: Kuznetsk | Statement: [Novokuznetsk, formerName, Kuznetsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kuznetsk
Context triple: [Novokuznetsk, formerName, Kuznetsk]
  • A. Kuznetsk
    Kuznetsk is a city in Penza Oblast, Russia, known as an industrial and transport center in the Volga region.
  • B. Novokuznetskaya
    Novokuznetskaya is a Moscow Metro station known for its distinctive Stalinist architecture and richly decorated interiors.
  • C. Nizhneangarsk
    Nizhneangarsk is a small urban locality in the Republic of Buryatia, Russia, situated at the northern tip of Lake Baikal and serving as a regional transport and administrative center.
  • D. Novokuznetsk chosen
    Novokuznetsk is a major industrial city in southwestern Siberia, Russia, known for its large metallurgical and coal-mining industries.
  • E. Kemerovo
    Kemerovo is an industrial city in southwestern Siberia, Russia, known as a center of the Kuzbass coal mining region.
  • 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_69e0b51f363c8190944000ab5523b02b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0cf89f08190bd7c0d552232d948 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:12 p.m.