Triple

T1386334
Position Surface form Disambiguated ID Type / Status
Subject South Pole E29853 entity
Predicate timeZonePractice P27238 FINISHED
Object New Zealand time at Amundsen–Scott Station 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: New Zealand time at Amundsen–Scott Station | Statement: [South Pole, timeZonePractice, New Zealand time at Amundsen–Scott Station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZonePractice
Context triple: [South Pole, timeZonePractice, New Zealand time at Amundsen–Scott Station]
  • A. capitalTimeZoneOf
    Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
  • B. timeZoneDependence
    Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
  • C. timeZoneType
    Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
  • D. timeZoneDesignation
    Indicates the specific time zone label or code assigned to an entity for representing its local time.
  • E. relatedTimeZone
    Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
  • 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_69a498dc92f8819094a1108f8ac90f43 completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c339f3d481909c04b14129899945 completed March 1, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69a4befe343c81909f758440a531b5be completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4c0335f7081908d50046ced4cdee0 completed March 1, 2026, 10:39 p.m.
Created at: March 1, 2026, 7:59 p.m.