Triple

T18737565
Position Surface form Disambiguated ID Type / Status
Subject Azimuth Airlines E458204 entity
Predicate focusCity P164 FINISHED
Object Mineralnye Vody 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: Mineralnye Vody | Statement: [Azimuth Airlines, focusCity, Mineralnye Vody]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mineralnye Vody
Context triple: [Azimuth Airlines, focusCity, Mineralnye Vody]
  • A. Mineralnye Vody chosen
    Mineralnye Vody is a town in Russia’s Stavropol Krai known as a key transport hub in the North Caucasus, particularly for its railway and airport connections.
  • B. Kislovodsk
    Kislovodsk is a Russian spa and resort city in the North Caucasus, renowned for its mineral springs and mountainous surroundings.
  • C. Borjomi
    Borjomi is a Georgian resort town famous for its mineral water springs and scenic location in the Borjomi Gorge.
  • D. Soligorsk
    Soligorsk is an industrial city in Belarus known for its large potash mining operations and location in the southern part of the Minsk Region.
  • E. Torzhok
    Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
  • 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_69d8d394dc308190b6725073f5db324c completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5768b80ac8190bc05628d64f86fc9 completed April 20, 2026, 12:42 a.m.
Created at: April 10, 2026, 11:51 a.m.