Triple

T6618523
Position Surface form Disambiguated ID Type / Status
Subject Mesa Airlines E149616 entity
Predicate callsign P1565 FINISHED
Object AIR SHUTTLE E119299 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: AIR SHUTTLE | Statement: [Mesa Airlines, callsign, AIR SHUTTLE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AIR SHUTTLE
Context triple: [Mesa Airlines, callsign, AIR SHUTTLE]
  • A. AIR SHUTTLE chosen
    AIR SHUTTLE is the radio callsign historically used by Mesa Airlines for its regional passenger flight operations in the United States.
  • B. Cargojet
    Cargojet is a Canadian cargo airline specializing in time-sensitive overnight air freight services across North America and select international routes.
  • C. Airlink
    Airlink is a South African regional airline that operates scheduled passenger services connecting smaller cities and remote destinations with major hubs in Southern Africa.
  • D. Sky Express
    Sky Express is a Greek regional airline that operates domestic flights connecting numerous islands and mainland cities within Greece.
  • E. Smartavia
    Smartavia is a Russian low-cost airline that operates domestic and regional flights, using Moscow Domodedovo International Airport as one of its main bases.
  • 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_69c687ed8a9c81908bb671717cb192ef completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af5b21348190b7f09045e9ec7d63 completed March 27, 2026, 4:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cbde37288190b1e65589aa09b676 completed March 27, 2026, 6:26 p.m.
Created at: March 27, 2026, 1:58 p.m.