Triple

T16923680
Position Surface form Disambiguated ID Type / Status
Subject Tajikistani ruble E410509 entity
Predicate replacedBy P101 FINISHED
Object somoni E391286 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: somoni | Statement: [Tajikistani ruble, replacedBy, somoni]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: somoni
Context triple: [Tajikistani ruble, replacedBy, somoni]
  • A. сомони chosen
    сомони — это денежная единица Таджикистана, названная в честь основателя таджикской государственности Исмоили Сомони.
  • B. Somosomo
    Somosomo is a coastal village on the Fijian island of Taveuni, known as a traditional center of chiefly authority and local administration.
  • C. sompoton
    The sompoton is a traditional bamboo mouth organ of the Dusun people of Sabah, Malaysia, known for its gourd wind chamber and soft, reedy sound used in folk music and ceremonies.
  • D. Sambali
    Sambali is an Austronesian language spoken by the Sambal people of the Zambales region in the Philippines.
  • E. SÖM
    SÖM is the vehicle registration code for the Sömmerda district in the German state of Thuringia.
  • 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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cdf06e8c81908028efef2faa6c6b completed April 18, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00cfd5e17481909fc4303fcc1342bf completed May 10, 2026, 6:35 p.m.
Created at: April 10, 2026, 5:30 a.m.