Triple

T17802806
Position Surface form Disambiguated ID Type / Status
Subject Razdolnaya River E444474 entity
Predicate hasSettlementOnBanks P57254 FINISHED
Object Ussuriysk 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: Ussuriysk | Statement: [Razdolnaya River, hasSettlementOnBanks, Ussuriysk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ussuriysk
Context triple: [Razdolnaya River, hasSettlementOnBanks, Ussuriysk]
  • A. Ussuriysk chosen
    Ussuriysk is a city in Russia’s Far East known as an important regional transport and economic center near the border with China.
  • B. Tuvan
    Tuvan is a Turkic language spoken primarily in the Tuva Republic of Russia, known for its rich oral traditions and association with Tuvan throat singing.
  • C. Bashkir
    Bashkir is a Turkic language spoken primarily by the Bashkir people in Russia’s Republic of Bashkortostan and surrounding regions.
  • D. Kalmyk
    Kalmyk refers to a Mongolic ethnic group primarily living in Russia’s Kalmykia region, known for being the only traditionally Buddhist people in Europe.
  • E. Sakha
    Sakha is a Turkic language spoken primarily in the Sakha Republic (Yakutia) in northeastern Siberia, Russia.
  • 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_69d8b9efe370819095cd219b143ae727 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4880171608190be2088c7a387bfb7 completed April 19, 2026, 7:45 a.m.
Created at: April 10, 2026, 10:13 a.m.