Triple
T4294681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Threadneedle Street |
E99681
|
entity |
| Predicate | hasTimeZoneOffset |
P4886
|
FINISHED |
| Object | UTC+0 |
—
|
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+0 | Statement: [Threadneedle Street, hasTimeZoneOffset, UTC+0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneOffset Context triple: [Threadneedle Street, hasTimeZoneOffset, UTC+0]
-
A.
hasNonIntegerHourOffset
Indicates that the time-related value or time zone differs from a reference time by an offset that is not a whole number of hours (e.g., includes 30- or 45-minute increments).
-
B.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
C.
timeOffsetType
Indicates the type or category of temporal offset that specifies how one time point is shifted relative to another.
-
D.
hasHalfHourOffset
Indicates that one entity’s time zone differs from another’s by an offset that includes a 30-minute (half-hour) component.
-
E.
isFixedOffsetFromUTC
chosen
Indicates that one time-related entity consistently differs from Coordinated Universal Time (UTC) by a specific, unchanging 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_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.