Triple
T7901692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IDT |
E183466
|
entity |
| Predicate | timeDifferenceFromISTInHours |
P26621
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [IDT, timeDifferenceFromISTInHours, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDifferenceFromISTInHours Context triple: [IDT, timeDifferenceFromISTInHours, 1]
-
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.
offsetFromBombayTime
Indicates the time difference between a given time reference and the local time in Bombay (Mumbai), typically expressed as an offset in hours or minutes.
-
D.
offsetFromCalcuttaTime
Indicates the time difference between a given time reference and the local time in Calcutta (Kolkata), typically expressed as an offset in hours or minutes.
-
E.
timeZoneSideIndia
Indicates that something is located on, associated with, or aligned to the India side of a time zone boundary or division.
- 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_69ca828d13088190b222be7aa9f9315c |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a40a0508190864479c2c41b12cb |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:02 p.m.