Triple
T34305971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LFRJ |
E880307
|
entity |
| Predicate | hasStandardTimeOffset |
P68829
|
FINISHED |
| Object | UTC+01:00 |
—
|
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+01:00 | Statement: [LFRJ, hasStandardTimeOffset, UTC+01:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardTimeOffset Context triple: [LFRJ, hasStandardTimeOffset, UTC+01:00]
-
A.
hasStandardTimeUTCOffset
chosen
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
-
B.
hasStandardTimeZone
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
C.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
D.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
E.
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).
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff8cecbf048190860b9f72b8753f5c |
completed | May 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69ff8c4c39dc8190b5bf35adc1bae7c6 |
completed | May 9, 2026, 7:34 p.m. |
Created at: May 1, 2026, 1:57 a.m.