Triple
T7018227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IST |
E162749
|
entity |
| Predicate | aheadOfUTCBy |
P19135
|
FINISHED |
| Object | 5 hours 30 minutes |
—
|
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: 5 hours 30 minutes | Statement: [IST, aheadOfUTCBy, 5 hours 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aheadOfUTCBy Context triple: [IST, aheadOfUTCBy, 5 hours 30 minutes]
-
A.
isAheadOfUTC
Indicates that a time, date, or timezone occurs at a later (positive offset) time than Coordinated Universal Time (UTC).
-
B.
hoursAheadOfUTC
chosen
Indicates the number of hours by which a given time or timezone is offset ahead of Coordinated Universal Time (UTC).
-
C.
hoursAheadOf
Indicates that one entity’s time is a specified number of hours ahead of another entity’s time.
-
D.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
E.
DSTIsAheadOfUTC
Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.