Triple

T16408122
Position Surface form Disambiguated ID Type / Status
Subject Dunedin Airport E398487 entity
Predicate timeZone P109 FINISHED
Object NZDT E13332 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: NZDT | Statement: [Dunedin Airport, timeZone, NZDT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NZDT
Context triple: [Dunedin Airport, timeZone, NZDT]
  • A. New Zealand Standard Time
    New Zealand Standard Time is the standard time zone observed in New Zealand, typically 12 hours ahead of Coordinated Universal Time (UTC+12).
  • B. Pacific/Auckland
    Pacific/Auckland is the IANA time zone identifier representing standard and daylight saving time for Auckland and most of New Zealand.
  • C. New Zealand Daylight Time chosen
    New Zealand Daylight Time is the daylight saving time zone used in New Zealand, typically observed during the Southern Hemisphere summer months.
  • D. NZ
    NZ is the IATA airline designator for Air New Zealand, the flag carrier airline of New Zealand.
  • E. NZ
    NZ is the vehicle registration code used for the Slovak town of Nové Zámky.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32870e44c8190aae7bc6e6022ceb7 completed April 18, 2026, 6:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00457d9f4081908a5f28eeafc44695 completed May 10, 2026, 8:44 a.m.
Created at: April 10, 2026, 5:09 a.m.