Triple

T21657559
Position Surface form Disambiguated ID Type / Status
Subject Narkomfin E534505 entity
Predicate shortName P43 FINISHED
Object Narkomfin 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: Narkomfin | Statement: [Narkomfin, shortName, Narkomfin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narkomfin
Context triple: [Narkomfin, shortName, Narkomfin]
  • A. Narkomfin chosen
    Narkomfin was the Soviet Union’s People’s Commissariat for Finance, the government body responsible for managing state financial and budgetary policy in the early USSR.
  • B. Narkomnats
    Narkomnats was a Soviet government body responsible for managing the affairs and policies related to the empire’s various nationalities and ethnic groups in the early years of the USSR.
  • C. Narkompros
    Narkompros was the Soviet government agency responsible for overseeing education, culture, and the arts in the early years of the USSR.
  • D. Narkomzem
    Narkomzem was the Soviet government body responsible for overseeing and managing agricultural policy and production in the USSR.
  • E. Lubyanka Building
    The Lubyanka Building is a historic Moscow structure infamous as the main Soviet-era security service complex, associated with political repression and state surveillance.
  • 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef5919c9c88190a2ddcf2cefee79a5 completed April 27, 2026, 12:39 p.m.
Created at: April 16, 2026, 6:36 p.m.