Triple

T9447602
Position Surface form Disambiguated ID Type / Status
Subject Midwest Airlines E227803 entity
Predicate callsign P1565 FINISHED
Object MIDEX E789333 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: MIDEX | Statement: [Midwest Airlines, callsign, MIDEX]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MIDEX
Context triple: [Midwest Airlines, callsign, MIDEX]
  • A. MIDEX chosen
    MIDEX is the radio callsign used by Midwest Connect, a former regional airline brand in the United States.
  • B. Medium Explorer (MIDEX)
    Medium Explorer (MIDEX) is a class of NASA astrophysics missions designed to conduct focused, mid-scale space science investigations with moderate budgets and mission scopes.
  • C. Reed Exhibitions
    Reed Exhibitions is a global events and trade show organizer known for producing large-scale exhibitions and conferences across diverse industries worldwide.
  • D. Messe Berlin
    Messe Berlin is a major exhibition and trade fair center in Berlin, Germany, hosting international trade shows, conferences, and large-scale events.
  • E. Hannover Messe
    Hannover Messe is one of the world’s largest and most influential industrial technology trade fairs, held annually in Hanover, Germany.
  • 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_69ca8439f8bc8190997f2ef40c9f0bc2 completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd7f62dfa48190bf318777d97f0f2a completed April 1, 2026, 8:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1106aeb708190bbbe1d05b7472194 completed April 4, 2026, 1:21 p.m.
Created at: March 30, 2026, 7:51 p.m.