Triple

T2908884
Position Surface form Disambiguated ID Type / Status
Subject QantasLink E63633 entity
Predicate hubAirport P8171 FINISHED
Object Adelaide Airport E73580 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: Adelaide Airport | Statement: [QantasLink, hubAirport, Adelaide Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adelaide Airport
Context triple: [QantasLink, hubAirport, Adelaide Airport]
  • A. Adelaide Airport chosen
    Adelaide Airport is the principal international and domestic airport serving the city of Adelaide and the state of South Australia.
  • B. Griffith Airport
    Griffith Airport is a regional airport serving the city of Griffith and the surrounding Riverina area in New South Wales, Australia.
  • C. Perth Airport
    Perth Airport is the main international and domestic airport serving the city of Perth and the wider Western Australia region.
  • D. Brisbane Airport
    Brisbane Airport is a major international and domestic airport in Queensland, Australia, serving Brisbane and acting as a key hub for several airlines.
  • E. Melbourne Airport (Tullamarine)
    Melbourne Airport (Tullamarine) is the primary international and domestic airport serving the city of Melbourne, 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_69ab4c44ab448190b9411324e8a1fc1d completed March 6, 2026, 9:51 p.m.
NER Named-entity recognition batch_69abe0d329c88190b6fcaef0be1799eb completed March 7, 2026, 8:24 a.m.
NED1 Entity disambiguation (via context triple) batch_69b2e80d295c8190920a2ef165dfdef4 completed March 12, 2026, 4:21 p.m.
Created at: March 6, 2026, 10:11 p.m.