Triple

T17846646
Position Surface form Disambiguated ID Type / Status
Subject Kfar Saba E445678 entity
Predicate hasSisterCity P919 FINISHED
Object Yessentuki 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: Yessentuki | Statement: [Kfar Saba, hasSisterCity, Yessentuki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yessentuki
Context triple: [Kfar Saba, hasSisterCity, Yessentuki]
  • A. Yessentuki chosen
    Yessentuki is a Russian spa city in the North Caucasus renowned for its mineral springs and health resorts.
  • B. Yelets
    Yelets is a historic city in western Russia known for its medieval origins, traditional lace-making, and role as a regional cultural and economic center.
  • C. Odintsovo
    Odintsovo is a town in western Russia that serves as an important suburban center just outside Moscow.
  • D. Ессентуки
    Ессентуки — город-курорт на Северном Кавказе в Ставропольском крае России, известный своими минеральными водами и санаторно-лечебными учреждениями.
  • E. Shadrinsk
    Shadrinsk is a town in Kurgan Oblast, Russia, known as an industrial and cultural center in the southern Ural region.
  • 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_69d8b9f26f18819089c9e43250bee6ae completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48ffb35248190a80a428686e06d87 completed April 19, 2026, 8:19 a.m.
Created at: April 10, 2026, 10:16 a.m.