Triple

T9101224
Position Surface form Disambiguated ID Type / Status
Subject IKAR E218159 entity
Predicate alsoKnownAs P39 FINISHED
Object Ikar Airlines E222352 NE FINISHED

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: Ikar Airlines | Statement: [IKAR, alsoKnownAs, Ikar Airlines]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ikar Airlines
Context triple: [IKAR, alsoKnownAs, Ikar Airlines]
  • A. Ikar Airlines chosen
    Ikar Airlines, operating under the brand name Pegas Fly, is a Russian charter and scheduled airline that primarily serves leisure destinations for tour operators.
  • B. Hunnu Air
    Hunnu Air is a Mongolian airline that operates domestic and regional international flights, primarily serving as a key carrier based in Ulaanbaatar.
  • C. Ibex Airlines
    Ibex Airlines is a Japanese regional airline that operates domestic routes, often connecting smaller cities and regional airports within Japan.
  • D. Yamal Airlines
    Yamal Airlines is a Russian regional airline based in the Yamalo-Nenets Autonomous Okrug that operates domestic and some international passenger services.
  • E. Aurora Airlines
    Aurora Airlines is a Russian regional carrier based in the Far East that operates domestic and some international flights, particularly serving remote communities in the Sakhalin and Khabarovsk regions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca83d9844081908e561e367fda6d45 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc971435d08190b5007ed44ac0a364 completed April 1, 2026, 3:55 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0182d8ea08190b4337a77b47019a5 completed April 3, 2026, 7:42 p.m.
Created at: March 30, 2026, 7:15 p.m.