Triple

T19365771
Position Surface form Disambiguated ID Type / Status
Subject Stornoway Airport E484396 entity
Predicate IATA code P2569 FINISHED
Object SYY NE NERFINISHED

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: SYY | Statement: [Stornoway Airport, IATA code, SYY]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SYY
Context triple: [Stornoway Airport, IATA code, SYY]
  • A. SYY chosen
    SYY is the IATA airport code for Stornoway Airport, which serves the town of Stornoway on the Isle of Lewis in Scotland’s Outer Hebrides.
  • B. ssy
    ssy is the ISO 639-3 language code for Saho, a Cushitic language spoken primarily in Eritrea and Ethiopia.
  • C. YSSY
    YSSY is the ICAO airport code for Sydney Kingsford Smith Airport, the primary international airport serving Sydney, Australia.
  • D. SYX
    SYX is the IATA airport code for Sanya Phoenix International Airport, a major civilian airport serving the resort city of Sanya on Hainan Island, China.
  • E. YYJ
    YYJ is the IATA airport code for Victoria International Airport, the main commercial air gateway serving Victoria on Vancouver Island in British Columbia, Canada.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619aa9ff48190b1ede47fb88a682e completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:35 p.m.