Triple
T1529579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calcutta Time |
E32409
|
entity |
| Predicate | timeZoneOffsetFromIST |
P26621
|
FINISHED |
| Object | −0:05:40 |
—
|
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: −0:05:40 | Statement: [Calcutta Time, timeZoneOffsetFromIST, −0:05:40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneOffsetFromIST Context triple: [Calcutta Time, timeZoneOffsetFromIST, −0:05:40]
-
A.
timeDifferenceWithIndianStandardTime
chosen
Indicates the time difference between a given time (or time zone) and Indian Standard Time (IST), typically expressed as an offset.
-
B.
differenceFromPakistanStandardTime
Indicates the time offset or deviation of a given time or timezone relative to Pakistan Standard Time.
-
C.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
D.
offsetFromAtlanticStandardTime
Indicates the time difference, in hours or minutes, between a given time reference and Atlantic Standard Time.
-
E.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
- 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.