Triple

T20337064
Position Surface form Disambiguated ID Type / Status
Subject Цхинвал E495641 entity
Predicate alternativeName P39 FINISHED
Object Тскхинвал 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: Тскхинвал | Statement: [Цхинвал, alternativeName, Тскхинвал]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Тскхинвал
Context triple: [Цхинвал, alternativeName, Тскхинвал]
  • A. Tskhinvali chosen
    Tskhinvali is the capital city of the breakaway region of South Ossetia in the South Caucasus, serving as its political and administrative center.
  • B. Tavaeli
    Tavaeli is a regional dialect of the Kaili language spoken by communities in Central Sulawesi, Indonesia.
  • C. Bolnisi
    Bolnisi is a town in southern Georgia known for its historic Bolnisi Sioni Cathedral and its diverse cultural heritage.
  • D. Tsakhuri
    Tsakhuri is an alternative name for the Tsakhur language, a Northeast Caucasian language spoken primarily in parts of Azerbaijan and Dagestan.
  • E. Bakuriani
    Bakuriani is a popular ski resort town in Georgia known for its alpine scenery, winter sports facilities, and role as a year-round mountain tourism destination.
  • 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_69e0b4a1a09881908d97270d6971a25a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e677ed75e081909bfc534033ac1c59 completed April 20, 2026, 7:01 p.m.
Created at: April 16, 2026, 11:23 a.m.