Triple

T30332749
Position Surface form Disambiguated ID Type / Status
Subject Frenkendorf E771530 entity
Predicate UTC_offset_DST P713 FINISHED
Object +2 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: +2 | Statement: [Frenkendorf, UTC_offset_DST, +2]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UTC_offset_DST
Context triple: [Frenkendorf, UTC_offset_DST, +2]
  • A. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • B. UTCOffsetStandardTime
    Indicates the time difference, in hours and minutes, that a location’s standard (non-daylight-saving) local time has from Coordinated Universal Time (UTC).
  • C. DSTAlternativePreviouslyUsedUTCOffset
    Indicates that a daylight saving time alternative has, at some point in the past, used a specific UTC offset.
  • D. utcOffsetDescription
    Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
  • E. DSTOffsetType
    Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
  • 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_69f2248aba24819095bb86480d55b23b completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f681c9bdf481908f50596dd90053aa completed May 2, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69f67603526c81908295a1ece8727c66 completed May 2, 2026, 10:09 p.m.
Created at: April 29, 2026, 7:53 p.m.