Triple
T34949829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Australia–South Australia border |
E1007958
|
entity |
| Predicate | marksTimeZoneChange |
P99943
|
FINISHED |
| Object | UTC+08:00 to UTC+09: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: UTC+08:00 to UTC+09:30 | Statement: [Western Australia–South Australia border, marksTimeZoneChange, UTC+08:00 to UTC+09:30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksTimeZoneChange Context triple: [Western Australia–South Australia border, marksTimeZoneChange, UTC+08:00 to UTC+09:30]
-
A.
timeZoneChange
chosen
Indicates a change in the time zone associated with an entity, such as shifting from one time offset or region-based time standard to another.
-
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.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
D.
timeZoneImplication
Indicates that one time zone condition or setting logically leads to, constrains, or determines another time zone condition or setting.
-
E.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.