Triple

T17254113
Position Surface form Disambiguated ID Type / Status
Subject Auckland Airport E418834 entity
Predicate timeZoneDST 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: [Auckland Airport, timeZoneDST, NZDT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: NZDT
Context triple: [Auckland Airport, timeZoneDST, 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42e6b2b1c8190b446ce648ecaad80 completed April 19, 2026, 1:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a017942ae108190ac6ec61514ba58b4 completed May 11, 2026, 6:37 a.m.
Created at: April 10, 2026, 5:39 a.m.