Triple
T2092249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras Time |
E32695
|
entity |
| Predicate | offsetFromBombayTime |
P34681
|
FINISHED |
| Object | +00:39 |
—
|
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: +00:39 | Statement: [Madras Time, offsetFromBombayTime, +00:39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offsetFromBombayTime Context triple: [Madras Time, offsetFromBombayTime, +00:39]
-
A.
timeDifferenceWithIndianStandardTime
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.
offsetFromJapanStandardTimeHours
Indicates the number of hours by which a time value is ahead of or behind Japan Standard Time.
-
D.
offsetFromAtlanticStandardTime
Indicates the time difference, in hours or minutes, between a given time reference and Atlantic Standard Time.
-
E.
differenceFromBangladeshStandardTime
Indicates the time offset between a given time reference and Bangladesh Standard Time.
- F. None of above. chosen
Provenance (4 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba7626d081908c9c0f18942e128d |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:43 p.m.