Triple
T456438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Standard Time |
E7241
|
entity |
| Predicate | hasNoSeasonalClockChanges |
P13686
|
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: [Georgia Standard Time, hasNoSeasonalClockChanges, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoSeasonalClockChanges Context triple: [Georgia Standard Time, hasNoSeasonalClockChanges, true]
-
A.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
-
B.
DSTChangeReason
Indicates the reason or cause for a change in daylight saving time status or rules.
-
C.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
D.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
E.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
- F. None of above. chosen
Provenance (4 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa1616481909399f92551a0c9e3 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede614b88190be07425f5535f56d |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ee8b56d08190bd625626353d01b4 |
completed | Feb. 28, 2026, 1:32 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.