Triple

T4259933
Position Surface form Disambiguated ID Type / Status
Subject Milwaukee Mitchell International Airport E96079 entity
Predicate FAAcode P420 FINISHED
Object MKE E427478 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: MKE | Statement: [Milwaukee Mitchell International Airport, FAAcode, MKE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MKE
Context triple: [Milwaukee Mitchell International Airport, FAAcode, MKE]
  • A. MKE
    MKE is the abbreviated name commonly associated with the Turkish sports club MKE Ankaragücü.
  • B. MKE chosen
    MKE is the three-letter IATA airport code for Milwaukee Mitchell International Airport, the primary commercial airport serving the Milwaukee, Wisconsin area.
  • C. Milwaukee
    Milwaukee is the largest city in Wisconsin, known for its brewing traditions, industrial history, and location on the western shore of Lake Michigan.
  • D. Milwaukie
    Milwaukie is a small city in northwestern Oregon, located just south of Portland along the Willamette River.
  • E. Orel
    Orel is a male given name most famously associated with former Major League Baseball pitcher Orel Hershiser.
  • 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_69b3454095ac81909c2494f7ff294af1 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34f7fe7348190baed8d214268b756 completed March 12, 2026, 11:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5c718a3188190851735afc3aa033f completed March 14, 2026, 8:37 p.m.
Created at: March 12, 2026, 11:06 p.m.