Triple

T36261482
Position Surface form Disambiguated ID Type / Status
Subject Pacific/Bougainville E892097 entity
Predicate previousTimeZoneOf P99943 FINISHED
Object Pacific/Port_Moresby 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/Port_Moresby | Statement: [Pacific/Bougainville, previousTimeZoneOf, Pacific/Port_Moresby]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previousTimeZoneOf
Context triple: [Pacific/Bougainville, previousTimeZoneOf, Pacific/Port_Moresby]
  • A. previousUTCOffset
    Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
  • B. timeZoneBeforeCession
    Indicates that the referenced time zone was in effect for a location before a specific cession or transfer of that territory occurred.
  • C. timeZoneChange chosen
    Indicates a change in the time zone associated with an entity, such as shifting from one time offset or region-based time standard to another.
  • D. relatedTimeZone
    Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
  • E. previousDSTOffsetFromUTC
    Indicates the difference in time (offset) from Coordinated Universal Time (UTC) that applied to an entity during the previous daylight saving time period.
  • 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_69f76e4699188190af045b11a840ce31 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ff8cecbf048190860b9f72b8753f5c completed May 9, 2026, 7:37 p.m.
PD Predicate disambiguation batch_69ff8c4c39dc8190b5bf35adc1bae7c6 completed May 9, 2026, 7:34 p.m.
Created at: May 3, 2026, 4:09 p.m.