Triple
T35732218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samara Time |
E1032786
|
entity |
| Predicate | previousStandardOffsetHours |
P5577
|
FINISHED |
| Object | +4 |
—
|
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: +4 | Statement: [Samara Time, previousStandardOffsetHours, +4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStandardOffsetHours Context triple: [Samara Time, previousStandardOffsetHours, +4]
-
A.
previousUTCOffset
chosen
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
B.
previousDSTOffsetFromUTC
Indicates the difference in time (offset) from Coordinated Universal Time (UTC) that applied to an entity during the previous daylight saving time period.
-
C.
previousTimeStandard
Indicates that one time standard directly preceded another in chronological use or official adoption.
-
D.
offsetFromStandardTime
Indicates the time difference between a given local time and the corresponding standard time for that location.
-
E.
offsetDSTDifferenceHours
Indicates the difference in time zone offsets, measured in hours, that results specifically from the application of daylight saving time.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.