Triple

T36261461
Position Surface form Disambiguated ID Type / Status
Subject Pacific/Bougainville E892097 entity
Predicate locatedInTimeZoneDatabase GENERATED
Object IANA time zone database UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInTimeZoneDatabase
Context triple: [Pacific/Bougainville, locatedInTimeZoneDatabase, IANA time zone database]
  • A. locatedInTimeZoneDatabaseCountry
    Indicates that the entity is situated in, or associated with, a country as defined in the time zone database.
  • B. locatedInTimeZone
    Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
  • C. isLocatedInTimeZoneRegion
    Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
  • D. locatedInTimeZoneUTCOffsetDST
    Indicates that an entity exists or operates in a time zone that observes daylight saving time with a specified UTC offset during that DST period.
  • E. timeZoneDatabase chosen
    Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
  • F. None of above.

Provenance (1 batch)

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.
Created at: May 3, 2026, 4:09 p.m.