Triple
T585513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide |
E15147
|
entity |
| Predicate | daylightSavingUtcOffset |
P713
|
FINISHED |
| Object | +10:30 |
—
|
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: +10:30 | Statement: [Adelaide, daylightSavingUtcOffset, +10:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daylightSavingUtcOffset Context triple: [Adelaide, daylightSavingUtcOffset, +10:30]
-
A.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
B.
DSTOffsetChange
Indicates a change in the time offset applied to a time zone due to the start or end of daylight saving time.
-
C.
differenceFromUSEasternDaylightTime
Indicates that one temporal value differs by a specified amount or offset from the time expressed in US Eastern Daylight Time.
-
D.
offsetInSecondsFromUTC
Indicates the time difference, measured in whole seconds, between a given time reference and Coordinated Universal Time (UTC).
-
E.
daylightSavingTimeName
Indicates the specific name or label used for the time zone during daylight saving time.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b9a46388190a094b9ebf8dec397 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c9315c8190a773e8e00737d8a0 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.