Triple
T4294682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threadneedle Street |
E99681
|
entity |
| Predicate | hasTimeZoneOffsetDST |
P713
|
FINISHED |
| Object | UTC+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: UTC+1 | Statement: [Threadneedle Street, hasTimeZoneOffsetDST, UTC+1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneOffsetDST Context triple: [Threadneedle Street, hasTimeZoneOffsetDST, UTC+1]
-
A.
DSTOffsetType
Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
-
B.
observesDSTOffset
Indicates that one entity follows or applies a specific daylight saving time (DST) offset in its timekeeping or scheduling.
-
C.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
D.
hasDSTComponent
Indicates that something includes or is associated with a component related to Daylight Saving Time (DST) behavior or configuration.
-
E.
timeZoneOriginDST
Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35083f87c8190a3d3b323e76ab575 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.