Triple
T697768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia/Hobart |
E13929
|
entity |
| Predicate | dstShift |
P4824
|
FINISHED |
| Object | +1:00 |
—
|
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: +1:00 | Statement: [Australia/Hobart, dstShift, +1:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstShift Context triple: [Australia/Hobart, dstShift, +1:00]
-
A.
offsets
Indicates that one entity counterbalances, compensates for, or reduces the effect, value, or impact of another.
-
B.
usesOffsetFrom
chosen
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
-
C.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
isOffsetFrom
Indicates that one entity’s position, value, or occurrence is displaced by a specified amount or direction relative to 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c99be48190babc37c397b6a186 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.