Triple
T4459208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anadyr Time |
E98209
|
entity |
| Predicate | previousUTCOffsetHistory |
P12951
|
FINISHED |
| Object | +12:00 standard with DST to +13: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: +12:00 standard with DST to +13:00 | Statement: [Anadyr Time, previousUTCOffsetHistory, +12:00 standard with DST to +13:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousUTCOffsetHistory Context triple: [Anadyr Time, previousUTCOffsetHistory, +12:00 standard with DST to +13:00]
-
A.
previousUTCOffset
Indicates the UTC time offset that applied to an entity (such as a timezone or location) immediately before the current or given offset.
-
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.
timeZoneHistorical
Indicates that there is a historical time zone relationship, specifying how an entity’s time zone (including offsets, rules, or changes) applied during past periods.
-
D.
historicalDSTUsage
Indicates that there was a period in the past when the entity or location observed daylight saving time, even if it may not do so currently.
-
E.
previousTimeStandard
Indicates that one time standard directly preceded another in chronological use or official adoption.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567184f481908a2787e4ac9bb345 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.