Triple

T1400205
Position Surface form Disambiguated ID Type / Status
Subject Port George VI Island Airport E30761 entity
Predicate IATACode P418 FINISHED
Object YTZ E30758 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: YTZ | Statement: [Port George VI Island Airport, IATACode, YTZ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YTZ
Context triple: [Port George VI Island Airport, IATACode, YTZ]
  • A. YQT
    YQT is the IATA airport code for Thunder Bay International Airport, a regional air transport hub in Thunder Bay, Ontario, Canada.
  • B. CYYZ
    CYYZ is the ICAO airport code for Toronto Pearson International Airport, Canada's largest and busiest air transport hub located in Mississauga, Ontario.
  • C. CYTZ chosen
    CYTZ is the ICAO airport code for Billy Bishop Toronto City Airport, a regional airport located on the Toronto Islands near downtown Toronto, Canada.
  • D. YAKT
    YAKT is the time zone abbreviation for Yakutsk Time, used in parts of eastern Russia.
  • E. AYT
    AYT is the IATA airport code for Antalya Airport, a major international gateway serving the resort city of Antalya on Turkey’s Mediterranean coast.
  • 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_69a498fd4e408190bd73eca30ea9754c completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c39c4c148190997150996ca26a99 completed March 1, 2026, 10:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad0156109081908f163af94e4e7978 completed March 8, 2026, 4:55 a.m.
Created at: March 1, 2026, 7:59 p.m.