Triple
T13959724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLST |
E335759
|
entity |
| Predicate | timeZoneOffsetFormat |
P34679
|
FINISHED |
| Object | UTC+05:30 |
—
|
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: UTC+05:30 | Statement: [SLST, timeZoneOffsetFormat, UTC+05:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneOffsetFormat Context triple: [SLST, timeZoneOffsetFormat, UTC+05:30]
-
A.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
B.
utcOffsetDescription
chosen
Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
-
C.
timeOffsetInHours
Indicates the temporal difference between two time points or events, measured in hours.
-
D.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
E.
timeZoneDatabaseFormat
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
- 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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e7b2f908190aa32f22298964746 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.