Triple

T11737200
Position Surface form Disambiguated ID Type / Status
Subject Runway 03L/21R E279059 entity
Predicate hasIATAAirportCode P2569 FINISHED
Object PTY E221235 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: PTY | Statement: [Runway 03L/21R, hasIATAAirportCode, PTY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PTY
Context triple: [Runway 03L/21R, hasIATAAirportCode, PTY]
  • A. PTY chosen
    PTY is the IATA airport code for Tocumen International Airport, the main international gateway serving Panama City, Panama.
  • B. PLY
    PLY is the National Rail station code for Plymouth railway station, a major rail hub in Plymouth, Devon, England.
  • C. PTR
    PTR was the abbreviation for the Physikalisch-Technische Reichsanstalt, the German national institute for standards and scientific-technical metrology in the early 20th century.
  • D. PTR
    PTR is the New York Stock Exchange ticker symbol for PetroChina Company Limited, one of China’s largest state-owned oil and gas producers.
  • E. PT
    PT is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Portugal in international standards and systems.
  • 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.