Triple

T1529580
Position Surface form Disambiguated ID Type / Status
Subject Calcutta Time E32409 entity
Predicate timeZoneOffsetFromUTCInMinutes P5579 FINISHED
Object 353.3333 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: 353.3333 | Statement: [Calcutta Time, timeZoneOffsetFromUTCInMinutes, 353.3333]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZoneOffsetFromUTCInMinutes
Context triple: [Calcutta Time, timeZoneOffsetFromUTCInMinutes, 353.3333]
  • A. offsetFromUTCInMinutes chosen
    Indicates the number of minutes by which a given time value differs from Coordinated Universal Time (UTC), positive or negative.
  • B. offsetInSecondsFromUTC
    Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
  • C. offsetFromUTCInHours
    Indicates the number of hours a time value is offset from Coordinated Universal Time (UTC), positive for time zones ahead and negative for those behind.
  • D. timeOffsetType
    Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
  • E. UTCOffsetDaylightSavingTime
    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_69a885ea86308190998f6bc14bb91f8e completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a933ddc5a881909cdf503f2bc29bd4 completed March 5, 2026, 7:42 a.m.
PD Predicate disambiguation batch_69a907ae8f688190ad9000ea1e018585 completed March 5, 2026, 4:33 a.m.
Created at: March 4, 2026, 7:26 p.m.