Triple
T148498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMT |
E3380
|
entity |
| Predicate | hasNoDaylightSavingOffset |
P384
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GMT, hasNoDaylightSavingOffset, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDaylightSavingOffset Context triple: [GMT, hasNoDaylightSavingOffset, true]
-
A.
UTCOffsetDaylightSavingTime
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
B.
observesDaylightSavingTime
chosen
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
C.
observesDaylightSavingWith
Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
typicalOffsetFromPacificTime
Indicates the usual time difference between a given time zone and Pacific Time (PT), without accounting for temporary variations like daylight saving changes.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a257ecb6f48190992c4c8ca908a81c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.