Triple

T3922505
Position Surface form Disambiguated ID Type / Status
Subject Pacific/Chatham E93192 entity
Predicate mainlandNewZealandTimeZone P51685 FINISHED
Object Pacific/Auckland LITERAL 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: Pacific/Auckland | Statement: [Pacific/Chatham, mainlandNewZealandTimeZone, Pacific/Auckland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainlandNewZealandTimeZone
Context triple: [Pacific/Chatham, mainlandNewZealandTimeZone, Pacific/Auckland]
  • A. isOneOfMainlandAustralianTimeZones
    Indicates that an entity is a time zone officially used in one of the mainland states or territories of Australia.
  • B. linkedToMainlandTimeZone
    Indicates that an entity’s time zone is synchronized with or derived from the primary mainland time zone of a region or country.
  • C. offsetFromNewZealandStandardTime
    Indicates the time difference between a given time reference and New Zealand Standard Time (NZST).
  • D. isThreeQuartersOfAnHourAheadOf
    Indicates that one entity’s time occurs exactly 45 minutes later than the other entity’s time.
  • E. capitalTimeZoneOf
    Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
  • F. None of above. chosen

Provenance (4 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_69aed96bfa1081908f7b30f2c647dee6 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeed7a553c81909b65f8287293ecac completed March 9, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69aee7609c4081908000ce12ae827c3f completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aeeb5f859c819095b61f5ba8eace4f completed March 9, 2026, 3:46 p.m.
Created at: March 9, 2026, 3:22 p.m.