Triple

T17102981
Position Surface form Disambiguated ID Type / Status
Subject Perth Airport E415024 entity
Predicate IATA code P2569 FINISHED
Object PER E415024 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: PER | Statement: [Perth Airport, IATA code, PER]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: PER
Context triple: [Perth Airport, IATA code, PER]
  • A. PER
    PER is the stock ticker symbol under which Perot Systems, an information technology services company founded by Ross Perot, was traded on public markets.
  • B. PER chosen
    PER is the IATA airport code for Perth Airport, the main international and domestic gateway serving Perth in Western Australia.
  • C. PER
    PER is the FIFA country code used to represent the Peru national football team in international competitions and official records.
  • D. PAR
    PAR is the IATA city code representing the collective airport system serving Paris, France, including major airports such as Charles de Gaulle and Orly.
  • E. PAR
    PAR is the standard abbreviation used for the Parramatta Eels, a professional rugby league club based in Sydney, Australia.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc2495c88190b5b16a006a994faf completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0139ffbe808190a24e827331ee4a6c completed May 11, 2026, 2:07 a.m.
Created at: April 10, 2026, 5:35 a.m.