Triple

T17943256
Position Surface form Disambiguated ID Type / Status
Subject SSJ100 E448636 entity
Predicate primaryOperator P5623 FINISHED
Object Aeroflot 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: Aeroflot | Statement: [SSJ100, primaryOperator, Aeroflot]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aeroflot
Context triple: [SSJ100, primaryOperator, Aeroflot]
  • A. Aeroflot chosen
    Aeroflot is Russia's largest and flag-carrying airline, headquartered in Moscow and operating an extensive network of domestic and international flights.
  • B. Rossiya Airlines
    Rossiya Airlines is a Russian airline based in Saint Petersburg that operates domestic and international passenger flights as part of the Aeroflot Group.
  • C. Ural Airlines
    Ural Airlines is a Russian airline based in Yekaterinburg that operates domestic and international passenger flights across Europe, Asia, and the Middle East.
  • D. Aerosvit Airlines
    Aerosvit Airlines was a now-defunct Ukrainian carrier that operated domestic and international flights, primarily from its main base in Kyiv.
  • E. Arkhangelsk Airlines
    Arkhangelsk Airlines was a Russian regional airline based in Arkhangelsk that later became known as Nordavia.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad97611c8190a861467ae51f6c48 completed April 19, 2026, 10:25 a.m.
Created at: April 10, 2026, 10:21 a.m.