Triple
T34676983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AKDT |
E890517
|
entity |
| Predicate | isDaylightVariantOf |
P6183
|
FINISHED |
| Object | Alaska Standard Time |
—
|
NE NERFINISHED |
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: Alaska Standard Time | Statement: [AKDT, isDaylightVariantOf, Alaska Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDaylightVariantOf Context triple: [AKDT, isDaylightVariantOf, Alaska Standard Time]
-
A.
isSummerTimeVariantOf
Indicates that one temporal or time-related entity is the daylight-saving (summer time) version of another standard-time entity.
-
B.
hasDaylightSavingVariant
chosen
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
C.
dayNightVariant
Indicates a relationship where one entity is a day-time version and the other is a night-time version of the same underlying thing.
-
D.
isDaylightSavingShift
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
-
E.
observesDaylightSavingWith
Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72325328881909479ba3ff5cc804f |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.