Triple

T34949831
Position Surface form Disambiguated ID Type / Status
Subject Western Australia–South Australia border E1007958 entity
Predicate hasAdjacentTimeZoneEast P721 FINISHED
Object Australian Central Standard Time NE NERFINISHED

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: Australian Central Standard Time | Statement: [Western Australia–South Australia border, hasAdjacentTimeZoneEast, Australian Central Standard Time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdjacentTimeZoneEast
Context triple: [Western Australia–South Australia border, hasAdjacentTimeZoneEast, Australian Central Standard Time]
  • A. adjacentTimeZoneEast chosen
    Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
  • B. adjacentTimeZoneWest
    Indicates that one time zone is directly to the west of another, sharing a common boundary without any other time zone in between.
  • C. isNeighboringTimeZoneTo
    Indicates that two time zones are directly adjacent to each other, typically sharing a common boundary or differing by one standard time offset step.
  • D. isOneHourAheadOf
    Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
  • E. hasTimeZoneDifferenceAlongBorder
    Indicates that two adjacent regions share a border across which their official time zones differ.
  • F. None of above.

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_69f76dc5d4308190b77553ee07b1ede6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fdd5fba5048190b7d430ae2054a1fd completed May 8, 2026, 12:24 p.m.
PD Predicate disambiguation batch_69fdd35f76f88190a1854ea27132f9c7 completed May 8, 2026, 12:13 p.m.
Created at: May 3, 2026, 4 p.m.