Triple

T11737199
Position Surface form Disambiguated ID Type / Status
Subject Runway 03L/21R E279059 entity
Predicate hasICAOAirportCode P419 FINISHED
Object MPTO E221236 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: MPTO | Statement: [Runway 03L/21R, hasICAOAirportCode, MPTO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MPTO
Context triple: [Runway 03L/21R, hasICAOAirportCode, MPTO]
  • A. MPTO chosen
    MPTO is the ICAO airport code for Tocumen International Airport, the main international gateway serving Panama City, Panama.
  • B. MTO
    MTO is an abbreviation for the Mediterranean Theater of Operations, the World War II combat zone encompassing Allied and Axis military campaigns around the Mediterranean Sea.
  • C. MTO
    MTO is the provincial government ministry responsible for transportation infrastructure, policy, and services in Ontario, Canada.
  • D. MTO
    MTO is the National Rail station code for Marton railway station in Middlesbrough, England.
  • E. MTS
    MTS is a public transportation agency that operates bus and rail services in the San Diego metropolitan area of California.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4ef1c4881909ad36dc27b1fe193 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f019b318188190bfb7effcf42974d2 completed April 28, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:41 p.m.