Triple

T10933298
Position Surface form Disambiguated ID Type / Status
Subject Navoi Region E258262 entity
Predicate currency P245 FINISHED
Object Uzbekistani soʻm E92057 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: Uzbekistani soʻm | Statement: [Navoi Region, currency, Uzbekistani soʻm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uzbekistani soʻm
Context triple: [Navoi Region, currency, Uzbekistani soʻm]
  • A. Uzbekistani soʻm chosen
    The Uzbekistani soʻm is the official fiat currency used in the Republic of Uzbekistan for all monetary transactions and economic activities.
  • B. Tajikistani somoni
    The Tajikistani somoni is the official national currency of Tajikistan, used for all forms of monetary transactions within the country.
  • C. Tajikistani ruble
    The Tajikistani ruble was the former national currency of Tajikistan used in the years following independence before being replaced by the somoni.
  • D. Kyrgyzstani som
    The Kyrgyzstani som is the official national currency of Kyrgyzstan, issued by the country's central bank and used for all major financial transactions.
  • E. Afghan rupee
    The Afghan rupee was the former currency of Afghanistan used before the introduction of the Afghan afghani.
  • 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_69d6aa8769b4819082bfe5e61b9017f0 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d770a16cbc8190acd619defed7114c completed April 9, 2026, 9:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69e2176328448190bbce6735ec97507a completed April 17, 2026, 11:20 a.m.
Created at: April 8, 2026, 9:23 p.m.