Triple
T14486300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AZT |
E359235
|
entity |
| Predicate | DSTAlternativePreviouslyUsed |
P29832
|
FINISHED |
| Object | AZST |
—
|
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: AZST | Statement: [AZT, DSTAlternativePreviouslyUsed, AZST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTAlternativePreviouslyUsed Context triple: [AZT, DSTAlternativePreviouslyUsed, AZST]
-
A.
historicalDSTUsage
Indicates that there was a period in the past when the entity or location observed daylight saving time, even if it may not do so currently.
-
B.
DSTNotRegularSince
Indicates that daylight saving time has not been regularly observed in the specified location since a given point in time.
-
C.
previouslyObservedDST
chosen
Indicates that the subject has been observed in a context where daylight saving time (DST) was in effect at some point in the past.
-
D.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
E.
DSTseason
Indicates that the relationship specifies the daylight saving time (DST) period or season during which a time-related event or setting is in effect.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.