Triple
T2883417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Central Daylight Time |
E59448
|
entity |
| Predicate | hasDSTComponent |
P42564
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Australian Central Daylight Time, hasDSTComponent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDSTComponent Context triple: [Australian Central Daylight Time, hasDSTComponent, yes]
-
A.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
B.
DSTType
Indicates the type or classification of daylight saving time (DST) applied to a given time zone or region.
-
C.
hasUniqueHalfHourDST
Indicates that the entity observes a daylight saving time offset that differs from standard time by a unique half-hour increment rather than a whole hour.
-
D.
isDaylightSavingTime
Indicates that the specified time or date falls within a period when daylight saving time rules are in effect.
-
E.
isDaylightSavingShift
Indicates that a change in local clock time occurs due to the start or end of daylight saving time.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02c238881908f7a349563c388bf |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:03 p.m.