Triple

T571149
Position Surface form Disambiguated ID Type / Status
Subject Belarus E13665 entity
Predicate currency P245 FINISHED
Object Belarusian ruble E6795 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: Belarusian ruble | Statement: [Belarus, currency, Belarusian ruble]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belarusian ruble
Context triple: [Belarus, currency, Belarusian ruble]
  • A. Belarusian ruble chosen
    The Belarusian ruble is the official currency of Belarus, introduced after the country gained independence from the Soviet Union.
  • B. Ukrainian hryvnia
    The Ukrainian hryvnia is the national currency of Ukraine, introduced in 1996 to replace the karbovanets and stabilize the country’s post-Soviet economy.
  • C. Soviet ruble
    The Soviet ruble was the official monetary unit of the USSR, used throughout the Soviet planned economy until the country's dissolution in 1991.
  • D. Russian ruble
    The Russian ruble is the official monetary unit of the Russian Federation, used for everyday transactions, government finances, and international trade involving Russia.
  • E. Armenian dram
    The Armenian dram is the official national currency of Armenia, used for everyday transactions and issued by the Central Bank of Armenia.
  • 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_69a4933fa4d88190a7949cc83c08c5c1 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49b483ac08190b3be152a7cf42011 completed March 1, 2026, 8:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4fc8475d881909e80d60fbb50c271 completed March 2, 2026, 2:57 a.m.
Created at: March 1, 2026, 7:33 p.m.