Triple

T16131625
Position Surface form Disambiguated ID Type / Status
Subject NZWN E391412 entity
Predicate identifies P310 FINISHED
Object Wellington Airport E88717 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: Wellington Airport | Statement: [NZWN, identifies, Wellington Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wellington Airport
Context triple: [NZWN, identifies, Wellington Airport]
  • A. Wellington Airport chosen
    Wellington Airport is the main international and domestic airport serving New Zealand’s capital city, Wellington, on the southern tip of the North Island.
  • B. Christchurch International Airport
    Christchurch International Airport is the main aviation gateway to New Zealand’s South Island, serving domestic and international flights for the city of Christchurch and the surrounding region.
  • C. Dunedin Airport
    Dunedin Airport is a regional international airport serving the city of Dunedin and the wider Otago region in New Zealand’s South Island.
  • D. Nelson Airport
    Nelson Airport is a regional airport in Nelson, New Zealand, serving as a key domestic hub with frequent connections to major New Zealand cities.
  • E. Nelson Airport
    Nelson Airport is a small regional airport serving the city of Nelson in southeastern British Columbia, Canada.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a02172c8190978f7951ccd80928 completed April 17, 2026, 11:31 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff7a0ed9c8190a10fa88ee94811cb completed May 10, 2026, 3:12 a.m.
Created at: April 10, 2026, 5:01 a.m.