Triple

T17640834
Position Surface form Disambiguated ID Type / Status
Subject Vitebsk Vostochny Airport E429218 entity
Predicate IATA code P2569 FINISHED
Object VTB 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: VTB | Statement: [Vitebsk Vostochny Airport, IATA code, VTB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: VTB
Context triple: [Vitebsk Vostochny Airport, IATA code, VTB]
  • A. VTB chosen
    VTB is the IATA airport code assigned to Vitebsk Vostochny Airport in Belarus.
  • B. VTB Insurance
    VTB Insurance is a Russian insurance company that provides a range of insurance products and services, operating as part of the VTB financial group.
  • C. VTB Bank
    VTB Bank is one of Russia’s largest state-controlled financial institutions, offering a wide range of banking and financial services domestically and internationally.
  • D. VTB Leasing
    VTB Leasing is a Russian leasing company that provides financing and leasing solutions for assets such as vehicles, equipment, and real estate, operating as part of the VTB financial group.
  • E. VKO
    VKO is the IATA airport code for Vnukovo International Airport, one of Moscow’s major international airports in 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46de50bf481909e938613b38f0202 completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 6:02 a.m.