Triple

T6483878
Position Surface form Disambiguated ID Type / Status
Subject SkyWest Airlines E146460 entity
Predicate callsign P1565 FINISHED
Object SKYWEST E146460 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: SKYWEST | Statement: [SkyWest Airlines, callsign, SKYWEST]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SKYWEST
Context triple: [SkyWest Airlines, callsign, SKYWEST]
  • A. SkyWest Airlines chosen
    SkyWest Airlines is a major North American regional airline that operates flights for several large U.S. carriers under their brand names.
  • B. Azimuth Airlines
    Azimuth Airlines is a Russian regional airline based in Rostov-on-Don, known for operating domestic and short-haul international routes primarily using Sukhoi Superjet 100 aircraft.
  • C. Tʼway Air
    Tʼway Air is a South Korean low-cost airline operating domestic and international routes across Asia and the Pacific.
  • D. Mesa Airlines
    Mesa Airlines is a U.S.-based regional airline that operates feeder flights for major carriers under their brand names.
  • E. Horizon Air
    Horizon Air is a regional airline in the United States that operates short-haul flights, primarily in the Pacific Northwest, as a subsidiary of Alaska Airlines.
  • 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_69c0090158c08190af0df9a2348d2d52 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a6de31c81909dd99d105f5bb4c2 completed March 22, 2026, 10:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65fd88d7c8190a98b7a48d49280c3 completed March 27, 2026, 10:45 a.m.
Created at: March 22, 2026, 4:52 p.m.