Triple

T2883409
Position Surface form Disambiguated ID Type / Status
Subject Australian Central Daylight Time E59448 entity
Predicate isNinetyMinutesAheadOf P42562 FINISHED
Object Australian Western Standard Time 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: Australian Western Standard Time | Statement: [Australian Central Daylight Time, isNinetyMinutesAheadOf, Australian Western Standard Time]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isNinetyMinutesAheadOf
Context triple: [Australian Central Daylight Time, isNinetyMinutesAheadOf, Australian Western Standard Time]
  • A. isOneHourAheadOf
    Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
  • B. isTwoHoursAheadOf
    Indicates that one entity’s time zone or local time is exactly two hours later than another entity’s.
  • C. isTwoHoursBehind
    Indicates that one entity’s time zone or clock is exactly two hours earlier than another entity’s time zone or clock.
  • D. isFourHoursBehind
    Indicates that one entity’s time zone or local time is exactly four hours earlier than another reference time or time zone.
  • E. isThreeHoursBehind
    Indicates that one entity’s time zone or local time is exactly three hours earlier than another entity’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_69ab4ac739188190a112f42a5a69c951 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abe02c238881908f7a349563c388bf completed March 7, 2026, 8:22 a.m.
PD Predicate disambiguation batch_69abdd15cbf08190bf7fea5ea516848a completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abdd96670c8190b727f9ac27dadf67 completed March 7, 2026, 8:11 a.m.
Created at: March 6, 2026, 10:03 p.m.