Triple

T21347162
Position Surface form Disambiguated ID Type / Status
Subject Izhevsk E526368 entity
Predicate hasIndustrialEnterprise P25392 FINISHED
Object Izhmekh 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: Izhmekh | Statement: [Izhevsk, hasIndustrialEnterprise, Izhmekh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Izhmekh
Context triple: [Izhevsk, hasIndustrialEnterprise, Izhmekh]
  • A. Izhmekh chosen
    Izhmekh is a major Russian arms manufacturer best known for producing Makarov pistols and other small arms in Izhevsk.
  • B. Kurskaya
    Kurskaya is a Moscow Metro station on the Koltsevaya (Circle) Line, serving as a major transfer hub in the city’s rapid transit network.
  • C. Amursk
    Amursk is a small industrial town in Russia’s Far East, situated on the Amur River and known for its timber and pulp-and-paper industries.
  • D. Sverdlov
    Sverdlov is a Russian surname most notably associated with Yakov Sverdlov, a prominent Bolshevik leader during the early Soviet period.
  • E. Fedorovskoye
    Fedorovskoye is a rural locality in Russia situated within the Tosnensky District of Leningrad Oblast.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee5ba8f1c8819089c5d753876b44d5 completed April 26, 2026, 6:38 p.m.
Created at: April 16, 2026, 4:56 p.m.