Triple

T35679393
Position Surface form Disambiguated ID Type / Status
Subject Ortacesus E1030961 entity
Predicate locatedInDSTTimeZoneOffsetFromUTC P713 FINISHED
Object +02:00 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: +02:00 | Statement: [Ortacesus, locatedInDSTTimeZoneOffsetFromUTC, +02:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInDSTTimeZoneOffsetFromUTC
Context triple: [Ortacesus, locatedInDSTTimeZoneOffsetFromUTC, +02:00]
  • A. 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.
  • B. locatedInTimeZone
    Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
  • C. timeZoneOffsetDestination
    Indicates the time difference (offset from a reference time, typically UTC) that applies to the destination location in a temporal or travel-related context.
  • D. DSTAlternativePreviouslyUsedUTCOffset
    Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
  • E. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • 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_69f76e0bb6608190ad3a1880be54a17d completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037c8d06cc8190ab6a5e18d9d2571e completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a04d8348190a4819666eab42c9b completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:05 p.m.