Triple
T4154209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America/Winnipeg |
E89976
|
entity |
| Predicate | dstOffsetChange |
P12951
|
FINISHED |
| Object | +1 hour |
—
|
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 hour | Statement: [America/Winnipeg, dstOffsetChange, +1 hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dstOffsetChange Context triple: [America/Winnipeg, dstOffsetChange, +1 hour]
-
A.
usesOffsetFrom
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
-
B.
historicalOffsetChanges
chosen
Indicates that the relationship captures past changes in an offset value between entities, including when and how that offset was modified over time.
-
C.
offsetFrom
Indicates that one entity is positioned or scheduled at a specific distance, time, or value away from another reference entity.
-
D.
offsets
Indicates that one entity counterbalances, compensates for, or reduces the effect, value, or impact of another.
-
E.
dstChangeControlledBy
Indicates that a change in destination (or target state) occurs under the control, influence, or decision of a specified agent or controller.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.