Triple

T2304881
Position Surface form Disambiguated ID Type / Status
Subject Indian/Christmas E51814 entity
Predicate timeZoneOffsetFromUTCInSeconds P4887 FINISHED
Object 25200 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: 25200 | Statement: [Indian/Christmas, timeZoneOffsetFromUTCInSeconds, 25200]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZoneOffsetFromUTCInSeconds
Context triple: [Indian/Christmas, timeZoneOffsetFromUTCInSeconds, 25200]
  • A. offsetInSecondsFromUTC chosen
    Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
  • B. timeOffsetType
    Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
  • C. timeOffsetReference
    Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
  • D. 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.
  • E. offsetFromUTCInMinutes
    Indicates the number of minutes by which a given time value differs from Coordinated Universal Time (UTC), positive or negative.
  • 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_69a88b0bb30c81908ded03b006d29387 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abce1f4f0c8190a714e4dcb8449f7e completed March 7, 2026, 7:05 a.m.
PD Predicate disambiguation batch_69abc58ce2a081908ce2f0cadd92e9f8 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:49 p.m.