Triple

T5208319
Position Surface form Disambiguated ID Type / Status
Subject Munich Airport E117566 entity
Predicate IATAcode P418 FINISHED
Object MUC E117567 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: MUC | Statement: [Munich Airport, IATAcode, MUC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MUC
Context triple: [Munich Airport, IATAcode, MUC]
  • A. MUC
    MUC is the abbreviation for the Meritorious Unit Commendation, a U.S. military unit award recognizing exceptionally meritorious conduct in the performance of outstanding services.
  • B. MUC chosen
    MUC is the IATA airport code for Munich Airport, a major international aviation hub in Germany.
  • C. MAU
    MAU (Media Access Unit) is a network device used in IEEE 802.5 Token Ring networks to connect multiple stations and manage the ring’s physical topology.
  • D. GUM
    GUM is a historic and iconic department store located on Red Square in Moscow, Russia, known for its grand architecture and luxury retail offerings.
  • E. GUM
    GUM is the IATA airport code for Antonio B. Won Pat International Airport, the main commercial airport serving Guam in the western Pacific.
  • 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_69bd4463dd3c81909966123f20b79d57 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd7a6d70d081908c74e86b3bca9ba2 completed March 20, 2026, 4:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69beefd4b75c8190b1b87b8d93925245 completed March 21, 2026, 7:21 p.m.
Created at: March 20, 2026, 1:47 p.m.