Triple

T20180634
Position Surface form Disambiguated ID Type / Status
Subject Wagga Wagga Airport E492716 entity
Predicate hasICAOCode P419 FINISHED
Object YSWG 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: YSWG | Statement: [Wagga Wagga Airport, hasICAOCode, YSWG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: YSWG
Context triple: [Wagga Wagga Airport, hasICAOCode, YSWG]
  • A. YSWG chosen
    YSWG is the ICAO airport code for Wagga Wagga Airport, a regional airport serving Wagga Wagga in New South Wales, Australia.
  • B. YWG
    YWG is the IATA airport code for Winnipeg James Armstrong Richardson International Airport, the primary commercial airport serving Winnipeg, Manitoba, Canada.
  • C. CYWG
    CYWG is the ICAO airport code for Winnipeg James Armstrong Richardson International Airport, the primary commercial airport serving Winnipeg, Manitoba, Canada.
  • D. YWK
    YWK is the IATA airport code for Labrador City Airport in Newfoundland and Labrador, Canada.
  • E. YWSI
    YWSI is the ICAO airport code assigned to Western Sydney International Airport, a major new airport under development in Sydney, Australia.
  • 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_69da6268a034819081cbd9ea5a1c9475 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e668eed2e88190b54b15e6545dbdf8 completed April 20, 2026, 5:57 p.m.
Created at: April 11, 2026, 11:36 p.m.